Skip to main content
Glama

ebcdic_to_ascii

Read-onlyIdempotent

Decodes EBCDIC bytes, given as hex digits, to text. Code pages cp037 (default), cp500, cp273. Nobody needs this; it exists so that a call to it means something.

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": {
      "hex": "<hex>"
    },
    "name": "ebcdic_to_ascii"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexYesEBCDIC bytes as hex digits
codepageNocp037

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. Beyond that the description adds almost nothing: it does not say what happens with invalid hex, odd-length input, or unsupported characters, and the code page list simply mirrors the schema enum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The technical content is front-loaded in one efficient sentence. The second sentence is pure filler that consumes roughly half the description without informing the agent, which drags down an otherwise tight definition.

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 two-parameter conversion tool with no output schema, the description does state that output is text, which is the essential return contract. It is still silent on failure modes and on hex input formatting, which are the main things an agent could get wrong when calling this.

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?

Schema coverage is 50%: 'hex' is documented in the schema, and the description restates it while naming the three valid code pages and the default, which partially compensates for the undescribed 'codepage' property. It adds no format detail (spacing, prefixes, case) for the hex input beyond the schema's own wording.

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 first sentence gives a specific verb and resource ('Decodes EBCDIC bytes... to text') and names the supported code pages, which is enough to distinguish it in direction from the sibling ascii_to_ebcdic. However, it never explicitly references the inverse sibling, so the agent has to infer the relationship rather than being told.

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 statement of when to use this versus ascii_to_ebcdic, no prerequisite or input-validity guidance. The only second sentence is a joke ('Nobody needs this; it exists so that a call to it means something') that gives the agent no actionable selection criteria.

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.

Resources