Skip to main content
Glama

Unicode normalization comparison

bpj_normalization_forms
Read-onlyIdempotent

Compare NFC, NFD, NFKC and NFKD text and code point lengths.

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

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that it reports code point lengths alongside text lengths, which is useful behavioral context, but says nothing about output structure, pagination, or the 6000-character input ceiling.

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 the comparison target front-loaded and no filler. It is perhaps too lean given the lack of output information, but nothing is wasted or buried.

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 one-parameter, read-only comparison tool this covers the essential what. However, with no output schema, the description should say what the comparison result looks like (per-form lengths, equality flags) and whether the input is truncated at 6000 characters.

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?

Single parameter with 0% schema description coverage — the schema only supplies a title ('Source text') and a maxLength of 6000. The description implies the input is the text to compare but adds no meaning about format, encoding assumptions, or what happens with the length limit.

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 ('Compare') and a specific resource (the four Unicode normalization forms) plus the metrics compared (text and code point lengths). This differentiates it from the single-form sibling bpj_dq_unicode_nfc, though it does not name that sibling explicitly.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the closely related bpj_dq_unicode_nfc or which one to pick when only checking a single form. Usage is only implied by the phrase 'Compare NFC, NFD, NFKC and NFKD'.

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.