Skip to main content
Glama

Decode a code point list

bpj_decode_codepoint_list
Read-onlyIdempotent

Decode whitespace-separated hexadecimal scalar values and reject surrogate code points.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, closed-world, non-destructive operation, so the description only needs to add behavior. It does add one real trait - surrogate code points are rejected - but says nothing about what happens on rejection (error vs partial output) or what the returned decoded text looks like.

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 no filler, front-loading the operation and then the input format constraint. Every element earns its place.

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 one-parameter pure decoder with no output schema and full annotation coverage, the definition is nearly sufficient. A brief note on failure behavior for rejected surrogates or the shape of the decoded result would close the last gap.

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?

Schema coverage is 0% and there is a single parameter, so the description must carry the meaning - and it does, defining 'text' as whitespace-separated hexadecimal scalar values, which is exactly what the schema's bare string type omits. The only gap is the 6000-character limit, which the schema itself documents.

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 precise input resource ('whitespace-separated hexadecimal scalar values'), which distinguishes it from decimal-HTML-reference and UTF-16 siblings by input format. It doesn't explicitly name a sibling it is not, so it stops short of 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?

The stated input format implies when to reach for it (you have a list of hex code points to turn into text), but there is no explicit when-to-use/when-not-use guidance, no prerequisite notes, and no named alternative among the decoding siblings.

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.