Skip to main content
Glama
Sign In

TokenSafe

by dev.tokensafe
OverviewDiscussionsAdmin

distill_prompt

Managed Cloud Distillation: compiles a verbose developer prompt into a dense TOCP S-expression server-side. Requires Solo/Team license.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "distill_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesNatural language developer prompt
context_hintNoOptional: short context hint for the distiller

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It usefully discloses two behavioral facts an agent cannot get elsewhere: processing is remote ('server-side', a data-egress implication) and a paid license tier is required. It is silent on cost, rate limits, latency, whether the prompt is retained, and what a failure looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core transformation and closed with the gating prerequisite. Nothing is repeated and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter tool with a fully documented schema, no annotations, and no output schema, the description covers the essentials of what goes in and roughly what comes out. It stops short of describing the returned structure or how to interpret the S-expression, which matters precisely because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented in structured form and the description adds no syntax, length, or format guidance. It doesn't even reference 'context_hint', so the baseline 3 applies rather than a higher mark.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb ('compiles') and a specific transformation ('verbose developer prompt' into a 'dense TOCP S-expression'), plus where it happens ('server-side'). An agent can tell this is a prompt-compression service. The 'TOCP S-expression' jargon is unexplained, but the input/output shape is inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'compiles a verbose developer prompt' — an agent can infer it is for condensing long prompts. The description adds a real prerequisite ('Requires Solo/Team license'), but states no when-not condition, no alternative (e.g. a local/offline distillation path), and no guidance on how the result should be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TokenSafe toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources