Skip to main content
Glama

Unicode scalar inventory

bpj_unicode_scalar_inventory
Read-onlyIdempotent

Group characters by Unicode code point and list their frequencies.

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

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 a closed-world scope, so the safety profile is fully covered. The description adds only the partitioning semantics (group by code point, report frequencies), and says nothing about ordering of results, whether case/encoding normalisation happens, or the 6000-character input cap.

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 tight sentence with no filler and the core operation front-loaded, but it has no structural elaboration (no statement of result ordering or output shape) so it is minimal rather than exemplary.

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 one-parameter read-only analysis tool, the essential purpose is covered, but with no output schema the description should sketch the return shape — e.g. whether it returns code point values, hex notation, and counts — and it does not. An agent knows what it does but not quite what it will get back.

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?

With one required parameter and 0% description coverage in the schema, the description only implicitly identifies the input as the text to analyse; it adds nothing about the 6000-character maxLength or what happens near that limit. The schema's 'Source text' title carries most of the meaning.

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 pair (group, list) and resource (characters by Unicode code point, frequencies), which differentiates it from sibling profilers like bpj_unicode_category_profile or bpj_unicode_script_profile by implying per-code-point granularity rather than category/script aggregation. It never explicitly names those siblings, so the differentiation is inferred rather than stated.

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?

Provides no when-to-use guidance, no exclusions, and no pointer to alternative unicode tools. An agent must guess whether per-code-point counting or a category/script/escape view is the right sibling.

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.