Skip to main content
Glama

Caelara Labs Agent Safety

context_chunker

Split text into token-bounded overlapping chunks

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": "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 observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It does state the two defining traits — chunks are token-bounded and overlap — which is meaningful and non-obvious. It omits what tokenizer defines a token, what the return structure is (presumably a list), and what happens when text is shorter than max_tokens, so gaps remain for a tool with zero annotation coverage.

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?

A single nine-word sentence with the core behavior front-loaded and no filler. Nothing in it is redundant with the schema in a wasteful way.

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?

This is a simple three-parameter pure function, and the description plus full schema coverage covers the inputs adequately. However, with no output schema, the return value (a list of chunk strings, and whether counts or offsets accompany them) is left entirely to inference, which is the main remaining gap.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description adds a little by tying "token-bounded" to max_tokens and "overlapping" to overlap, confirming the unit is tokens rather than characters. It does not restate defaults, which is fine since the schema already carries them.

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?

"Split text into token-bounded overlapping chunks" gives a specific verb (split), resource (text), and two qualifiers that define the output shape. An agent can tell this is a text-segmentation utility, though nothing in the text distinguishes it from token_compressor or explains how the two differ.

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 when-to-use guidance, no mention of prerequisites, and no routing to or away from alternatives such as token_compressor. The agent must infer from the name alone that this is the tool for pre-chunking long input.

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