Skip to main content
Glama

Decode decimal character references

bpj_decode_decimal_html_references
Read-onlyIdempotent

Decode semicolon-terminated decimal scalar references; leave invalid values unchanged.

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

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine behavioral detail beyond that: it only handles semicolon-terminated forms and leaves invalid values unchanged, which tells the agent the tool is non-throwing on malformed input. It omits what happens to plain text or unterminated references.

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 compact sentence with the decoding scope front-loaded and the fallback behavior trailing. No filler, no restatement of the title.

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 simple pure transform with rich annotations and no output schema, the definition covers the core contract, but it leaves open how non-reference text and unterminated/hex references are treated in the output. A brief note on output shape would complete it.

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 required parameter and 0% schema description coverage, the schema contributes only "Source text" and maxLength 6000. The description implicitly characterizes the input as text containing decimal references but adds no detail on format, encoding expectation, or behavior at 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?

Names a specific verb ("Decode") and a narrowly scoped resource ("semicolon-terminated decimal scalar references"), which is enough for an agent to know this turns numeric character references into characters. It does not, however, distinguish itself from nearby decoders such as bpj_decode_codepoint_list or bpj_decode_utf8_strict, leaving the boundary implicit.

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 named alternative. The agent must infer from the name alone that this applies to HTML decimal references while hex references and other encodings are handled elsewhere.

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.