Skip to main content
Glama

Get one invoice

invoice_detail
Read-onlyIdempotent

One invoice's numbers: line items, subtotal, tax, total, payments received and balance due. Takes an invoice id. No PDF. Read only.

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": {
      "invoiceId": "<invoiceId>"
    },
    "name": "invoice_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceIdYesThe invoice's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / invoiceId / description
      Previous value: -"The invoice_id from invoice_list"New value: +"The invoice's id"
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'Read only' line is largely redundant. The one piece of genuinely additive behavior is 'No PDF', which clarifies the response format; nothing is said about permissions, currency, or missing-invoice handling.

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?

Three short fragments, front-loaded with what the agent gets back, then the input, then exclusions. No sentence is padding.

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?

For a one-parameter read tool with rich annotations, the description covers input, output contents and the PDF exclusion. Because there is no output schema, the field enumeration does real work, though error behavior for an invalid id is unaddressed.

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?

Single parameter with 100% schema description coverage, so the schema carries the load and the baseline is met. 'Takes an invoice id' adds no format or sourcing detail beyond the schema, but there is only one parameter, so nothing is left meaningfully ambiguous.

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?

Names the resource (one invoice) and enumerates the returned figures: line items, subtotal, tax, total, payments, balance due. The singular framing implicitly distinguishes it from invoice_list, though it never names that sibling explicitly.

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?

'Takes an invoice id' plus 'No PDF' sets a useful scope boundary and tells the agent not to expect document delivery. It gives no explicit when-to-use-this-vs-invoice_list guidance, leaving routing to be inferred from the singular resource.

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.