mcptoon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
| extensions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| demo_build_tool_manifestA | Reduces a set of MCP tool definitions, grouped by server or flat, to the names-only index mcptoon puts in front of an agent — one line per server listing its tool names, no schemas — with the estimated token drop against the text you supplied. ... |
| demo_compare_formatsA | Encodes one JSON document as JSON, TOON and Compact renderings and returns each form's character count, estimated token count and percentage saved against the JSON baseline — the way to measure mcptoon's output compression on a payload you actually have. ... |
| demo_decode_toonA | Parses TOON text into a JSON value and returns it, together with a canonical serialisation for comparing against the original — the way to prove an encode_toon round trip is lossless. Use it on text this server produced or on a stored TOON document; to produce such text use encode_toon, and to compare formats rather than parse use compare_formats. ... |
| demo_describe_runtimeB | Describes the running demo server itself: mcptoon version, the MCP protocol versions it accepts, the interpreter and platform versions behind it, and whether it carries any third-party runtime dependency. ... |
| demo_echo_messageA | Returns the submitted message text back unchanged, in one text content block, as a reachability probe for this server's stdio framing. Use it to confirm the MCP handshake and the transport work before testing anything else; it produces no analysis of its own, so for size comparisons call compare_formats and for a token figure call estimate_tokens. ... |
| demo_encode_toonA | Converts a JSON document into TOON, the line-oriented format mcptoon can serve in place of JSON, and returns the encoded text. Use it when you need the encoded form by itself; to see it next to the other formats with savings percentages use compare_formats, and to read such text back use decode_toon. ... |
| demo_estimate_tokensA | Counts the tokens in a text you supply using the estimator this package ships — character count divided by four, floored — so its numbers are directly comparable with the savings reported by build_tool_manifest and compare_formats. ... |
| demo_list_supported_agentsB | Reports the AI agent configuration targets mcptoon's sync command knows how to write, each with the path it resolves to in this process's environment. ... |
| demo_report_benchmark_rowsA | Returns this project's committed token measurements for 5, 50 and 255 MCP tool definitions encoded with tiktoken cl100k_base: raw JSON, TOON, SLIM and Compact token counts with each format's percentage saved. ... |
| demo_simplify_tool_schemaA | Rewrites a single MCP tool definition (name, description, inputSchema) into mcptoon's slim form, where each parameter keeps only its name, its type and its required marker, and returns the slim definition with the character and estimated-token delta against what you sent. ... |
| demo_validate_config_draftA | Checks a proposed mcptoon server configuration before you save it and reports problems per entry: an entry with neither command nor url, one that sets both, args or env of the wrong JSON type, keys mcptoon ignores, and which transport mcptoon would choose. ... |
| mcptoon_manifestA | List the upstream tools this gateway currently exposes, grouped by server. Returns names by default; that compact view is what an agent should read instead of pulling every full schema. Pass include_descriptions for a one-line summary per tool. |
| mcptoon_serversA | Report the MCP servers configured behind this gateway: transport, tool count and whether their tools loaded. Use it to see what is actually reachable before calling a tool, and to spot a server that configured but published nothing. |
| mcptoon_healthA | Self-check of this gateway process: version, config path, servers configured, tools indexed and uptime. Read this first when a tool you expect is missing; it distinguishes an empty config from a server that failed to load. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes, but there is some overlap: mcptoon_manifest, demo_build_tool_manifest, and demo_simplify_tool_schema all deal with tool definitions and could be confused. demo_estimate_tokens and demo_compare_formats also both report token counts. Descriptions clearly differentiate them, but an agent might still hesitate.
Two naming conventions are mixed: mcptoon_* for gateway tools and demo_* for demo tools. Within each group, there is a consistent verb_noun pattern (snake_case), but the two prefixes create inconsistency across the set.
14 tools is a reasonable count for a gateway that exposes both management and demo capabilities. It is slightly heavy due to many demo tools, but each tool seems to serve a distinct purpose.
The gateway covers essential management (manifest, servers, health) and demo operations (encode, decode, compare, estimate, etc.). Missing are operations for modifying server configurations or managing tools, but the core read-only monitoring and demo functionality is complete.