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 |
|---|---|
| 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. |
| mcptoon_usageA | How much this gateway has saved: tools compressed, tokens saved and the session call count. Call this when you want to tell the user what mcptoon did. Report these numbers verbatim; never estimate them yourself. |
| mcptoon_skillsA | List the skills mcptoon indexes on this machine: slug and one-line description per skill. Read it once to learn what skills exist, then resolve the one you need with mcptoon_resolve_skills. Offline and read-only; pass include_aliases to also see alias cards. |
| mcptoon_resolve_skillsA | Return the skills that best match a task description, best first. Call this with the user's request before acting, then read the chosen skill's SKILL.md. Offline BM25 ranking, no LLM. |
| mcptoon_inspectA | Show one upstream tool's full input schema — the parameters to call it with. Read-only; nothing runs. Use it after mcptoon_manifest names a tool. |
| mcptoon_callA | Run any upstream tool by its namespaced name (server_tool). Under the default compact exposure the tool list is withheld, so this is how you run one found via mcptoon_manifest. Arguments are validated first. |
| mcptoon_retrieveA | Get back the full, uncompressed text of a tool result mcptoon compressed. When a result ends with a line naming a handle, call this if the summary lacks a detail you need. |
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 9 tools
Most tools target clearly distinct operations: manifest lists tools, inspect shows a schema, call runs one, retrieve decompresses output, and skills/resolve_skills are separate (list vs. rank). There is mild overlap between health, servers, and usage (all report gateway state), but descriptions draw usable boundaries.
Every tool uses the same mcptoon_ snake_case prefix, which is highly consistent. The suffixes mix single-word nouns (health, manifest, servers, skills, usage) with verbs (retrieve, call, inspect) plus resolve_skills, so it's predictable but not a strict verb_noun pattern.
Nine tools is well-scoped for a gateway that must expose discovery, schema inspection, invocation, decompression, and diagnostics. Each tool earns its place with no redundancy.
The surface covers the full gateway lifecycle: discover servers (servers), list tools (manifest), inspect schemas (inspect), invoke (call), decompress (retrieve), plus skills and usage diagnostics. A keyword search over tools (distinct from skills resolution) is the only noticeable gap.