Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-publish-1792555732020-textkit---unicode-no

textkit - unicode normalize NFC/NFD: Normalize text to NFC, NFD, NFKC or NFKD and report the first differing position.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-publish-1792555732020-textkit---unicode-no"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses that the result includes a first-differing-position report, which is real behavioral value. However it never says what is being compared, whether the operation is idempotent, or what the response looks like, leaving a meaningful gap for a zero-annotation tool.

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 naming the family, the tool, and the operation, followed by the behavior clause. Dense but readable, with no filler; the only cost is that the two ideas are crammed together.

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?

No annotations and no output schema, so the description must justify itself, and it does state the operation and a piece of output behavior. It falls short on input expectations and on how the differing-position result is produced, which an agent needs before invoking.

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

Parameters4/5

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

Zero declared parameters, so the baseline of 4 applies and the description does enumerate the four accepted normalization forms. The schema is an empty object even though the tool plainly needs input text, and the description never says how the text is supplied, so the implicit contract remains underspecified.

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?

Names a specific verb (normalize) and resource (Unicode text to NFC/NFD/NFKC/NFKD), which separates it from nearby siblings such as x402-normalize-whitespace or x402-remove-accents. The added clause about reporting the first differing position muddies the purpose slightly, since it implies a comparison step the description never explains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the normalization-form enumeration, but there is no explicit when-to-use or when-not, and no pointer to plausible alternatives (x402-normalize, x402-to-unicode, x402-from-unicode, x402-remove-accents) that an agent would otherwise have to disambiguate against.

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.