Skip to main content
Glama

Fold fullwidth ASCII

bpj_fullwidth_ascii_fold
Read-onlyIdempotent

Map fullwidth ASCII and ideographic space to ordinary ASCII while preserving other characters.

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

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 establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description's useful addition is the preservation guarantee ('while preserving other characters'), which tells the agent the transform is narrow rather than a blanket normalization. It does not mention the 6000-character input cap or what the operation returns, leaving gaps the annotations cannot fill.

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 sentence with zero wasted words, front-loading the action and character classes before the preservation clause. Nothing to trim and nothing misordered.

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 pure string transform with no output schema and full annotation coverage, the definition is nearly sufficient: the input class, output class, and preservation rule are all stated. The main omission is the input length ceiling and any note that output is a plain transformed string.

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 a single parameter at 0% schema description coverage, the description should carry the burden but only implicitly identifies the input as the text to fold; it adds no naming, format, or limit detail. The 6000-character maximum is visible only in the schema, and nothing in the description reinforces it.

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 ('Map') plus the exact character classes affected (fullwidth ASCII and ideographic space) and the non-effect ('preserving other characters'). An agent can distinguish it from siblings like bpj_diacritic_fold or bpj_ascii_entity_transcription by the input class alone, though no sibling is named 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 statement of when to use this tool versus alternatives such as bpj_diacritic_fold or bpj_ascii_entity_transcription, and no exclusions or prerequisites. Usage is only inferable from the character classes named in the purpose sentence.

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.