Skip to main content
Glama

Strictly decode UTF-8

bpj_decode_utf8_strict
Read-onlyIdempotent

Reject malformed UTF-8 byte sequences and recover the original Unicode string.

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": {
      "bytes": "<bytes>"
    },
    "name": "bpj_decode_utf8_strict"
  }
}

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value by stating that malformed sequences are rejected rather than silently substituted, which tells the agent to expect failure on bad input. It stops short of saying what that failure 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the strictness constraint front-loaded and no filler. It is efficient, though extremely terse for a tool whose only parameter needs explanation.

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 one-parameter read-only tool with no output schema, the description covers the return value at a high level ('the original Unicode string'). It omits the input encoding (hex), the length limit, and the shape of a rejection, all of which an agent needs to call it correctly the first time.

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?

There is one parameter with 0% schema description coverage, so the burden falls on the description, which says nothing about the 'bytes' argument. The schema's title field ('Hexadecimal bytes') and maxLength of 3000 carry the encoding and size constraints instead, leaving the description with no added parameter meaning.

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 ('decode') and resource (UTF-8 byte sequences), plus the distinguishing strictness policy of rejecting malformed input and recovering the Unicode string. It does not explicitly contrast itself with sibling decoders such as bpj_decode_codepoint_list, but the operation is unambiguous.

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 mention of when to prefer this over a lenient decoder, and no note on prerequisites. The word 'Strictly' in the title hints at a policy distinction but the description never routes the agent between alternatives.

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.