render

Overview ¶

Package render turns jade's typed responses into plain text for the MCP transport.

The consumer of every jade response is a language model, not a parser. MCP already delivers tool results as text content, so JSON is a serialization tax paid on every call: braces, quotes, repeated field names, indentation, and nulls for fields nobody populated. The 8.3 benchmark measured that tax at 5.63x shell's token cost across seven realistic questions, with roughly every response landing at 1,100-1,600 tokens regardless of how small the actual answer was.

Rendering happens at the transport boundary, so the internal structs stay typed and testable and only the wire format changes.

House style, applied by every renderer here:

• the decisive content comes first, on the first line where possible;
• empty, null and zero-valued fields are omitted entirely rather than serialized as evidence of their own absence;
• source code is emitted as source code, not as a quoted string with escaped newlines;
• structure appears only where a caller must branch on it.