Skip to main content
Glama

Grapheme boundaries

bpj_grapheme_boundaries
Read-onlyIdempotent

List UTF-16 start and end offsets of grapheme clusters, preserving combining marks and emoji sequences.

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_grapheme_boundaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a genuine behavioral guarantee ('preserving combining marks and emoji sequences') and, absent an output schema, hints at the return shape ('start and end offsets'), though it never says whether results are pairs, objects, or ordering. Adequate but not rich.

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?

One sentence, front-loaded with the operation and its output, with the preservation guarantee attached as a qualifier. No filler and nothing buried.

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 one-parameter, read-only offset calculator with full annotation coverage, the description supplies the essential facts: what is returned (UTF-16 start/end offsets) and the key semantic guarantee about combining marks and emoji. Only the return structure granularity and the input length limit are left unstated.

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 coverage is 0% and the description never mentions the single 'text' parameter, its role as the source string, or the 6000-character limit. The parameter is self-evident from its title and type, so this lands at the minimum-viable baseline rather than a real gap.

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 ('List') and resource ('UTF-16 start and end offsets of grapheme clusters'), which is enough to distinguish it from the similarly named bpj_truncate_grapheme_budget by operation. It does not, however, explicitly contrast itself with that sibling, so an agent must infer the difference from the name alone.

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: an agent can infer this is the tool for enumerating grapheme cluster positions rather than truncating text, but the description never states when to choose it or when to prefer the truncation sibling. No exclusions, prerequisites, or alternatives are given.

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.