Skip to main content
Glama

Latin diacritic folding

bpj_diacritic_fold
Read-onlyIdempotent

Remove combining marks attached to Latin letters while preserving marks in other scripts.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds one useful behavioral fact beyond that - non-Latin marks are preserved - but says nothing about precomposed characters (e.g., whether 'é' is decomposed and folded), normalization form, or what happens to non-combining letters like 'ø'.

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 core action front-loaded and the scoping caveat second; no filler. It could have used the same space to add one clarifying clause about precomposed input instead of nothing.

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, idempotent read-only text transform with annotations covering safety and a single obvious string parameter, the definition is close to sufficient. The remaining gap is the precomposed-vs-combining distinction, which materially changes the output and is not addressed.

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?

One parameter with 0% schema description coverage: the schema only supplies a title and a 6000-character cap. The description never mentions the text input, the length limit, or whether input may contain mixed scripts, so it does not compensate for the coverage gap.

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+object: 'Remove combining marks attached to Latin letters,' and adds a scope clause preserving marks in other scripts. This distinguishes it from a generic fold, though it does not name a sibling like bpj_fullwidth_ascii_fold as an alternative, so it stops short of a 5.

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 only implied by the scope clause: the agent can infer this is for Latin text and must not be used where non-Latin marks matter. There is no explicit when-to-use, when-not-to-use, or alternative (e.g., fullwidth folding, Unicode normalization) named.

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.