Skip to main content
Glama

compress_prompt

Compress verbose developer prompts into dense TOCP S-Expressions to reduce token usage and context bloat while preserving request intent.

Instructions

Compresses a verbose developer prompt into an ultra-dense TOCP S-Expression via DeepSeek-V3 / Regex.

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": "compress_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesNatural language request from developer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.4

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the method (DeepSeek-V3 / Regex) but omits whether compression is lossy or reversible, whether an external API call is made, failure modes, and permission or rate-limit requirements.

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?

The description is a single front-loaded sentence with no wasted words. The key action, input, output format, and method are all packed efficiently.

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 simple one-parameter tool, the description covers the input and output format, but with no annotations and no output schema it should say more about the returned S-Expression and behavioral constraints. It is adequate but leaves meaningful gaps.

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 the single prompt parameter is already documented. The description adds only the qualifier 'verbose' beyond the schema's 'Natural language request from developer', which is marginal added meaning.

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?

The description states a specific verb (compresses), resource (verbose developer prompt), and output format (ultra-dense TOCP S-Expression), so the tool's function is clear. It does not explicitly differentiate itself from the sibling compact_conversation, but the prompt-vs-conversation distinction is implied.

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

Usage Guidelines2/5

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

Usage is only implied by the phrase 'verbose developer prompt'; there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent must infer that this is for prompt compression rather than conversation compaction.

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