Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_agent_context_chunker

Split text into token-bounded overlapping chunks with configurable max tokens and overlap to keep agent context within limits and preserve continuity.

Instructions

[Agent Safety] Split text into token-bounded overlapping chunks 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_context_chunker"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to chunk
overlapNoOverlap tokens (default 50)
max_tokensNoMax tokens per chunk (default 500)

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?

No annotations are supplied, so the description carries the full burden. It does disclose latency (p50 11 ms, p95 15 ms) and the serving endpoint, which is genuine behavioral context, but it omits the return shape (presumably a list of chunk strings), any input size limits, and error behavior.

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?

The core sentence is short and front-loaded, but the benchmark timestamp/URL and hosted-endpoint line are marketing boilerplate that consume roughly half the text without helping the agent invoke the tool. The run-on punctuation ('chunks Measured p50...') also impairs parsing.

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 three-parameter tool this is close to adequate, but there is no output schema and the description never says what comes back, which is the main open question an agent would have before calling a chunker.

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 text, overlap (default 50), and max_tokens (default 500) are already documented in the schema. The description adds nothing about parameter interaction (e.g., that overlap must be smaller than max_tokens), so the baseline 3 applies.

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?

States a specific verb and resource: 'Split text into token-bounded overlapping chunks'. An agent immediately knows the operation. It does not, however, distinguish itself from the sibling token_compressor, which an agent might reasonably confuse with chunking.

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 chunk vs. when to use token_compressor or other siblings, no mention of prerequisites, and no exclusions. The '[Agent Safety]' prefix hints at a category but does not tell the agent when this tool is the right choice.

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