Skip to main content
Glama

ASCII numeric reference transcription

bpj_ascii_entity_transcription
Read-onlyIdempotent

Represent non-ASCII characters with hexadecimal character references for ASCII-only storage.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 openWorldHint=false, so the safety profile is covered by structured data. The description adds the intent (ASCII-only storage) but says nothing about the emitted form (e.g. '&#xE9;' versus bare hex), how already-ASCII text passes through, or what happens near the 6000-character limit.

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 short sentence with the operation front-loaded and no filler; nothing is redundant. It is arguably over-terse rather than padded, so brevity is not the problem here.

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, annotation-rich, output-schema-less transform, the definition is minimally viable: the intent is clear but the result format and edge-case behaviour are unspecified, which matters because the tool's whole value is the shape of the emitted references.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning and it effectively does not: it never states that the single 'text' argument is the string to be transformed, nor does it mention the 6000-character cap. Only a weak inference ('non-ASCII characters') connects the description to the input.

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?

The description names a concrete operation ('Represent non-ASCII characters with hexadecimal character references') plus the motivation ('for ASCII-only storage'), so an agent can tell this is an encoding/transcription transform rather than a detector or counter. It does not differentiate itself from adjacent ASCII-normalisation siblings such as bpj_fullwidth_ascii_fold, leaving the exact transformation boundary to inference.

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 when-to-use guidance, no precondition (e.g. 'use when output must be pure ASCII for downstream systems'), and no statement of when this is the wrong tool versus folding or escaping alternatives. The purpose clause hints at a context but nothing is explicit.

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.