Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_agent_token_compressor

Compress text to a chosen ratio of its original length to reduce token load in agent workflows.

Instructions

[Agent Safety] Compress text to a target ratio of its original length Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://agent.caelaralabs.com.

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": "caelara_agent_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 observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does add real behavioral facts: latency percentiles and the backend endpoint called. However, it omits the traits that matter most for a text transformer — whether compression is lossy, what the output looks like, whether the result is deterministic, and whether any size limits apply.

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

Conciseness3/5

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

It is short and front-loads the core operation, which is good. The benchmark timestamp and the endpoint URL read as vendor boilerplate rather than information an agent needs to select or invoke the tool.

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 two-parameter tool with full schema coverage, the description is adequate on inputs. Because there is no output schema, a sentence on the return value (a shortened string, presumably) would close the main remaining gap.

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 'text' and 'ratio' are already documented with their range and default. The description's phrase 'target ratio of its original length' restates the schema rather than adding format, edge-case, or clamping behavior.

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 and resource ('Compress text to a target ratio of its original length'), which is unambiguous about the operation. It does not distinguish itself from neighboring text-processing siblings such as caelara_agent_context_chunker, so it stops short of a 5.

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 statement of when to use this tool, when not to, or which alternative to pick. The '[Agent Safety]' prefix hints at a category but gives no decision criteria for an agent choosing between it and the other agent-oriented utilities.

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

Deploy Server

Other Tools