Skip to main content
Glama
Sign In
Akamai Cloud MCP Server

Akamai Cloud MCP Server

Official
by akamai-developers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

linode_list_invoices

Read-only

Retrieve a list of account invoices with date, subtotal, tax, and total. Payment-method detail is redacted for security.

Instructions

List the account's invoices with date, subtotal, tax, and total. Payment-method detail is redacted.

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

Input Schema

NameRequiredDescriptionDefault
detailNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, which is consistent. The description adds value by specifying that payment-method detail is redacted, a behavioral trait beyond the annotation. It also lists the fields returned.

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 a single, concise sentence with no unnecessary words. It front-loads the main purpose and includes key details efficiently.

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 an output schema present, the description does not need to detail return values. It covers the main fields and the redaction trait. However, it omits pagination or filtering details that might be expected for a list tool.

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?

The optional parameter 'detail' is not described in the description. Schema description coverage is 0%, so the description should compensate but fails to explain its purpose or effect.

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?

The description clearly states the tool lists invoices with specific fields (date, subtotal, tax, total) and mentions redaction of payment-method detail. It distinguishes this from other list tools by its focus on invoices, though no explicit differentiation from sibling tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like linode_estimate_cost or linode_get_account. It does not specify prerequisites or context for its use.

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