Skip to main content
Glama

ascii_to_ebcdic

Read-onlyIdempotent

Encodes ASCII text to EBCDIC bytes, returned as hex digits. Code pages cp037 (default), cp500, cp273.

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": "ascii_to_ebcdic"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesASCII text to encode
codepageNocp037

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely new context: the output is hex digits and the default code page is cp037. It stops short of describing hex formatting details (spacing, byte order) or error behavior.

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?

Two short sentences, zero filler, with the encoding direction and return format front-loaded. Every clause carries information an agent would otherwise have to infer.

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?

With no output schema, the description correctly states the return format (hex digits). For a two-parameter pure converter this is nearly complete; only hex formatting conventions and handling of non-ASCII input are unstated, which are minor within a closed-world encoding tool.

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 only 50% – the 'codepage' parameter has an enum but no schema description. The description compensates by naming all three supported code pages and marking cp037 as the default, which is exactly the missing meaning an agent needs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Encodes ASCII text to EBCDIC bytes') and the output form ('returned as hex digits'). The direction is unambiguous and immediately distinguishable from the sibling ebcdic_to_ascii without opening either schema.

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?

No explicit when-to-use or when-not guidance, and the reverse sibling is never named. Usage is only implied by the encoding direction, which is clear enough for a simple converter but not spelled out.

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