Skip to main content
Glama

Split text into sized chunks

bpj_chunk_text
Read-onlyIdempotent

Split by a maximum code-point count with a preference for nearby whitespace. Chunks rejoin to the original text.

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>",
      "size": "<size>"
    },
    "name": "bpj_chunk_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds one genuinely useful behavioral guarantee beyond them — 'Chunks rejoin to the original text' (lossless, no characters dropped) — plus the heuristic that boundaries prefer whitespace, but says nothing about the return shape or what happens when a single token exceeds the limit.

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?

Two tight sentences with zero filler, and the operative constraint (max code points, whitespace preference) is front-loaded before the rejoin guarantee. Nothing is repeated from the schema or annotations.

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

Completeness4/5

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

For a two-parameter, read-only, idempotent utility with no output schema and well-titled params, the description covers the core contract — unit of measurement, boundary heuristic, and reversibility. The main residual gap is the return type (an ordered list of chunks) and edge-case behavior, which an agent must infer.

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 0%, so the description carries more burden, but the schema titles already label both parameters ('Maximum code points per chunk', 'Text'). The description confirms the code-point unit and adds that boundaries are whitespace-preferred, which explains why chunks may be shorter than `size`; it says nothing about how `text` is consumed or what an empty/oversized input yields.

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') plus the governing rule ('maximum code-point count with a preference for nearby whitespace'), which is enough to distinguish it from the unrelated siblings such as bpj_search_text_context or bpj_text_inspect. It stops short of explicitly naming a sibling it is not, so it lands just below the top band.

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

Usage Guidelines3/5

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

Usage is only implied: the size ceiling and whitespace preference suggest this is the tool for fitting text under a length limit, but there is no explicit when-to-use statement, no prerequisites, and no pointer to an alternative for other text operations. Minimum viable guidance.

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.