Skip to main content
Glama

Word boundary segments

bpj_word_boundary_segments
Read-onlyIdempotent

List word-like segments and their UTF-16 start positions using English locale Unicode segmentation.

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": "bpj_word_boundary_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the segmentation rule in effect (English locale Unicode) and the index unit (UTF-16), which is genuine behavioral context. It stops short of saying whether non-word tokens, whitespace, or punctuation are included in the output and what happens at the 6000-character limit.

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, naming the verb, output, and algorithm in sequence. It is slightly jargon-dense ('English locale Unicode segmentation') without unpacking what that implies for edge cases, which keeps it off a 5.

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 one-parameter, no-output-schema tool this is close to adequate: it states what is returned (segments plus start positions) and the unit of those positions. Missing details include whether indices are 0-based, whether segments are returned in text order, and whether non-word tokens appear, all of which matter since no output schema exists to answer them.

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 schema supplies only the title 'Source text' and a maxLength of 6000. The description does not explicitly characterize the text parameter, though the segmentation context makes its role self-evident and the boundary unit (UTF-16) is useful for interpreting results.

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 uses a specific verb ('List') and a specific resource ('word-like segments and their UTF-16 start positions'), plus the segmentation standard used ('English locale Unicode segmentation'). It does not, however, distinguish itself from nearby siblings such as bpj_json_pointer_segments or bpj_adjacent_word_echo, so an agent must infer the difference from names alone.

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?

The description contains no when-to-use guidance, no exclusions, and does not name an alternative for related tasks like counting words or finding adjacent echoes. The only implied usage is that this tool segments text, which is already obvious from the title.

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.