Skip to main content
Glama

Invoice (order to cash)

o2c_get_invoice
Read-onlyIdempotent

Invoice with lines and what is still open on it.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "o2c_get_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYesThe invoice. An existing invoice id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description contributes the useful detail that the response includes line items and remaining open balance, but says nothing about not-found behavior or what 'open' means when a payment is partially applied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no waste, front-loading the resource. The phrasing 'what is still open on it' is slightly informal but conveys the key content efficiently.

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

Completeness3/5

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

With no output schema, the description carries the burden of describing return values, and it does so only partially (lines and open amounts). It omits the single-invoice-by-id framing, error cases, and whether open amounts include credits or unapplied cash.

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?

There is a single parameter with 100% schema description coverage ('An existing invoice id'), so the schema carries the semantics. The description adds nothing about the id format or where to obtain it; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and title establish that this retrieves an invoice, and the description adds that the payload includes lines and open amounts. However, it never states the verb or scope explicitly, and it does not distinguish itself from sibling readers such as solo_get_invoice or o2c_get_order.

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?

There is no statement of when to use this tool, no prerequisites (e.g. needing a known invoice id from o2c_get_order), and no mention of the near-identical solo_get_invoice alternative. Usage must be inferred entirely from the name.

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.