Skip to main content
Glama

Inspect UTF-16 code units

bpj_utf16_code_units
Read-onlyIdempotent

Display the hexadecimal UTF-16 code units and their offsets in the supplied string.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 output shape (hex code units plus offsets), which is useful, but omits notable behavioral details such as how astral characters are split into surrogate pairs and the 1500-character input cap. With annotations carrying the safety burden, a 3 is appropriate.

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?

One front-loaded sentence with no filler; the verb and output content come first. It is arguably too terse for a tool whose semantics hinge on surrogate-pair behavior, but nothing in it is wasted.

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 single-input inspection tool this covers the essentials: what is computed and roughly what is returned. Without an output schema, however, the description should say more about the return structure (per-unit entries vs. a formatted table) and about astral-plane characters, which are the main correctness concern for UTF-16 inspection.

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

Parameters2/5

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

Schema description coverage is 0% – the single parameter only carries a title ('Unicode text') and maxLength 1500. The description says merely 'the supplied string' and does not clarify encoding expectations, surrogate-pair handling, or what happens to input beyond the length limit, so it does not compensate for the coverage gap on the only parameter.

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 ('Display') and a precise resource ('hexadecimal UTF-16 code units and their offsets') for a supplied string, which is meaningfully different from sibling inspectors like bpj_inspect_uuid or bpj_text_inspect. It does not, however, explicitly contrast itself with the closest sibling bpj_text_inspect, leaving the agent to infer the distinction 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?

There is no when-to-use or when-not-to-use guidance, no mention of when an agent should inspect UTF-16 units instead of general text inspection, and no prerequisites or constraints stated. Usage is only inferable from the purpose sentence itself.

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.