Skip to main content
Glama

Encode Adobe Ascii85

bpj_adobe_ascii85
Read-onlyIdempotent

Encode four-octet groups as Adobe Ascii85 with zero compression and a shortened trailing group.

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

Input Schema

NameRequiredDescriptionDefault
bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that ('zero compression', 'shortened trailing group'), which tells the agent the output is uncompressed and how partial blocks are handled. However it omits other defining traits of the Adobe variant, such as the <~ ~> delimiters and whether line breaks are emitted, which materially affect the result.

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?

One compact sentence, front-loaded with the verb and target encoding, with no filler. It is arguably over-terse for the information it needs to carry, but nothing is wasted or buried.

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?

This is a simple single-parameter pure function with annotations and no output schema, so most of the burden is light. Still, an agent cannot tell from the definition that the input must be hex-encoded nor what the returned string looks like (delimiters, wrapping), which are the two facts needed to invoke and consume it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter and 0% schema description coverage, the description should compensate but does not: it never says the 'bytes' input is a hexadecimal string, nor how odd-length or non-hex input is handled, nor what the 3000-character cap implies. The only hint ('four-octet groups') concerns grouping during encoding, not the parameter's format, so the agent must fall back on the schema title alone.

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 and resource ('Encode ... as Adobe Ascii85') plus two qualifying behaviors (zero compression, shortened trailing group), so the transform is identifiable without opening the schema. It does not name a sibling or contrast with a plain/generic Ascii85 or Base85 encoder, so it falls short of full differentiation.

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?

Usage is only implied: an agent can infer this is the tool for producing Adobe-flavored Ascii85 output when no compression is wanted. There is no explicit when-to-use statement, no mention of when the compressed/zlib variant would be preferred, and no prerequisites 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.