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

readonly-mcp-akamai

by desty2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_groups

Retrieve account groups in the Akamai hierarchy, returning group names, IDs, parent relationships, and associated contract IDs.

Instructions

List account groups in the Akamai hierarchy. Returns group names, IDs, parent relationships, and associated contract IDs.

Example questions:

  • "What groups exist in the Akamai account?"

  • "Show me the account structure"

  • "Which contracts are associated with each group?"

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior2/5

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

No annotations provided, and the description does not mention behavioral aspects such as idempotency, side effects, rate limits, or authentication requirements. For a read-only list tool, some transparency about safety (e.g., 'this is a read-only operation') would be helpful.

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 extremely concise: two sentences plus example questions. Every part adds value without redundancy.

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?

The description covers the essential output fields for a simple list tool. Since an output schema exists, the agent can infer exact structure. No filtering or pagination info is needed for a basic list-all.

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?

No parameters exist, so the description does not need to explain them. Baseline for 0 parameters is 4. The description adds value by detailing what the response contains (group names, IDs, etc.).

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 'List account groups in the Akamai hierarchy' and specifies returned fields (names, IDs, parent relationships, contract IDs). It is distinct from siblings which target different resources like edgeworkers or DNS zones.

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 provide clear usage context ('What groups exist?'). Although not explicitly stating when not to use, the list of siblings shows that other tools serve different purposes, so confusion is unlikely.

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