Skip to main content
Glama

Caelara Labs Agent Safety

token_compressor

Compress text to a target ratio of its original length

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": {
      "text": "<text>"
    },
    "name": "token_compressor"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to compress
ratioNoTarget ratio 0.1-0.9 (default 0.5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden and falls well short. It never states whether compression is lossy, what happens to semantic content, whether ratio applies to characters or tokens, or what the output looks like—all critical for a tool that alters text content.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the behavioral detail noted elsewhere rather than through disciplined editing.

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

Completeness2/5

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

For a text-transforming tool with no annotations and no output schema, the definition should explain lossiness, output format, and ratio semantics. None of that is present, leaving the agent to guess at the most consequential behaviors.

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, establishing a baseline of 3. The phrase 'of its original length' adds a small clarification about what ratio means, but nothing about ratio edge cases or the default beyond what the schema already says.

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 gives a specific verb (compress) and resource (text) with an explicit outcome: hitting a target ratio of original length. It does not differentiate itself from nearby tools like context_chunker or pii_redactor, so an agent can't tell from the text why it would compress rather than chunk.

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?

There is no guidance on when to use this tool versus alternatives, no mention of when compression is inappropriate, and no prerequisites. The only context for choosing it comes from the tool name and the sibling list, not from the definition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources