Skip to main content
Glama

UTF-8 width histogram

bpj_utf8_byte_histogram
Read-onlyIdempotent

Count code points by their UTF-8 byte width and report the total byte count.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety behavior is covered. The description adds the substantive behavior that it counts code points grouped by byte width and also totals bytes, but says nothing about the 6000-character cap, how oversized input is handled, or how degenerate input (empty string) is reported.

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 tight sentence with the primary operation front-loaded and the secondary output appended. Every clause contributes and there is no filler.

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 simple single-parameter analysis utility with no output schema, the description conveys both the grouping (by UTF-8 byte width) and the extra aggregate (total bytes) an agent needs to know it returns a histogram-like result. Only the concrete return shape and input-limit behavior are left unstated, which is minor at this complexity.

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?

Only one parameter exists and schema description coverage is 0%, so the description must carry some weight. It implies the input is the text being analyzed by code point, which matches the 'Source text' schema property, but it adds no detail about the 6000 maxLength constraint or character-encoding expectations.

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 names a specific operation (counting code points by UTF-8 byte width) and an additional output (total byte count), which distinguishes it usefully from byte-offset and decoding siblings. It does not explicitly name or contrast with those siblings, so it falls short of a 5.

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 statement of when to prefer this over bpj_utf8_byte_offsets or bpj_design_tracking_width, nor any mention of prerequisites or exclusions. The agent must infer applicability from the name and one-line purpose alone.

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.