Skip to main content
Glama

Get an invoice

get_invoice
Read-onlyIdempotent

Use this when the user asks about one sales invoice by number or id: its lines, total, VAT, balance or status ("show me INV-0042"). One invoice by invoice_id or invoice_number: client name and TRN, lines, subtotal, VAT, total, amounts paid and credited, balance (remaining), status, due date, and app_url, a link that opens it in Fatura Go for the signed-in user. No client contact details. Do not use it to list several invoices (list_invoices) or to change one (update_draft_invoice).

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

Input Schema

NameRequiredDescriptionDefault
invoice_idNo
business_idNoFrom list_businesses. May be left out: the invoice is then looked up in every business shared with this connection.
invoice_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: it enumerates the returned fields (lines, subtotal, VAT, total, paid/credited, balance, status, due date, app_url) and explicitly bounds the result with "No client contact details" and a user-scoped link. It does not address what happens when no identifier is supplied or when the invoice is not found, which keeps it below 5.

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?

The trigger and the identifier constraint are front-loaded, and the exclusions come last where they are easy to act on. The middle field-enumeration sentence is dense but earns its place because there is no output schema to describe the response.

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 no output schema, enumerating the returned fields and noting the absent contact details is exactly the right compensation for a read tool. The remaining gap is failure/validation behavior when identifiers are missing or an invoice is not found, which matters given all three parameters are optional.

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 coverage is only 33% (business_id is the only documented parameter), so the description does carry weight by stating the lookup works "by invoice_id or invoice_number". However, with zero required parameters it never clarifies whether one of the two identifiers must be supplied, nor what happens if both are given or if neither is, leaving a real ambiguity. That is baseline-plus rather than compensating fully for the coverage gap.

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 opens with a specific trigger ("when the user asks about one sales invoice by number or id") and names the resource and scope precisely, including the "one invoice" constraint. It also names the siblings it is not (list_invoices, update_draft_invoice), so an agent can distinguish it without reading any other schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use with a concrete example utterance ("show me INV-0042") and explicit when-not-to-use routing to list_invoices for multiple invoices and update_draft_invoice for mutations. Both alternatives are real siblings, so the routing is actionable rather than decorative.

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.

Resources