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

readonly-mcp-akamai

by desty2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_edgeworker_versions

Retrieve version history for an EdgeWorker, including identifiers, creation dates, and checksums.

Instructions

List versions for an EdgeWorker. Returns version identifiers, creation dates, and checksums.

Example questions:

  • "What versions exist for EdgeWorker 42?"

  • "When was the latest version created?"

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": {
      "edgeworker_id": "<edgeworker_id>"
    },
    "name": "list_edgeworker_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeworker_idYesEdgeWorker ID (numeric)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided; description indicates a read-only operation (returns version info) with no side effects mentioned. Adequate for a simple list tool, but lacks details on permissions or pagination.

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?

Concise description: two sentences plus example questions, front-loaded with purpose. No extraneous content.

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 output schema present, description covers core functionality and return data. Minor omission of pagination or ordering is acceptable for a list tool.

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 covers 100% of parameter descriptions; description adds minimal value beyond examples. Baseline 3 is appropriate.

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 lists versions for an EdgeWorker and specifies the returned data (identifiers, dates, checksums). It is distinct from sibling tools like list_edgeworkers which lists edgeworkers themselves.

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?

Example questions illustrate when to use (e.g., 'What versions exist for EdgeWorker 42?') but no explicit guidance on when not to use or alternatives among siblings.

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