Skip to main content
Glama

Decimal digit block inventory

bpj_unicode_decimal_blocks
Read-onlyIdempotent

Group decimal digits by the zero code point of their ten-character decimal block.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered and the description need not restate it. The sentence does add one behavioral clue — results are grouped by block zero code point rather than listed per character — but it says nothing about what happens to non-digit input or how mixed-script text is partitioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no filler and the operation is front-loaded, which is good. However, it is terse to the point of opacity — 'ten-character decimal block' is unexplained jargon, and the sentence is spent on mechanism rather than on what the agent gets back.

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?

With no output schema, the description carries the burden of explaining the return shape, and it does only partially — 'group by zero code point' hints at a mapping but not at the keys, ordering, or counts. Behavior on text with no decimal digits at all is unspecified.

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% for the single 'text' parameter, so the schema only supplies a name, a title, and a 6000-char bound. The description never clarifies what 'text' should contain (arbitrary script text? digits only?) or whether non-digits are tolerated, leaving the only input undocumented in both places.

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 verb (group) and a specific resource (decimal digits, keyed by the zero code point of their ten-character decimal block), which is precise in Unicode terms and plausibly distinguishes it from scalar/category inventory siblings. It stops short of contrasting itself with any sibling by name, and the domain jargon ('decimal block', 'zero code point') requires prior knowledge to interpret.

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 guidance, no stated preconditions, and no mention of when an agent should prefer this over bpj_unicode_scalar_inventory or bpj_unicode_category_profile. The reader must infer the use case (script-level digit analysis) entirely.

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.