Skip to main content
Glama
Sign In
readonly-mcp-akamai

readonly-mcp-akamai

by desty2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

translate_error_code

Convert Akamai error reference codes into plain-language details: HTTP response, client/server IPs, origin info, failure reason, and WAF details.

Instructions

Translate an Akamai error reference code into human-readable details. Returns HTTP response code, client/server IPs, origin info, failure reason, and WAF details.

Example questions:

  • "What does error 9.6f64d440.1318965461.2f2b078 mean?"

  • "Translate this Akamai error reference"

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": {
      "error_code": "<error_code>"
    },
    "name": "translate_error_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
error_codeYesAkamai reference error code (e.g., 9.6f64d440.1318965461.2f2b078)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It lists what the tool returns and implies a read-only, non-destructive operation, but does not explicitly state this or mention other behavioral traits.

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?

The description is two concise paragraphs: the first defines purpose and output, the second provides example queries. Every sentence adds value, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description appropriately summarizes return fields. Combined with examples and clear purpose, it provides complete contextual guidance for a simple translation 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?

The schema covers the single parameter with a description and example. The description adds value by providing concrete error code examples and clarifying the input format, going beyond the schema alone.

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?

The description clearly states the tool translates a specific Akamai error code into human-readable details, listing the returned fields. It is distinct from sibling tools, which focus on retrieving configurations or lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Example questions effectively indicate when to use the tool. However, no explicit guidance on when not to use it or alternatives is provided, though siblings do not overlap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools