Skip to main content
Glama

Get one of my invoices

portal_invoice_get
Read-onlyIdempotent

Details of one of your own commercial invoices by number (e.g. CI-0001): lines, charges, discount, totals per currency, payment stages, paid and remaining amounts and the bank account printed on the document. Someone else's or unknown number returns not found. Free text is wrapped as data.

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": {
      "ref": "<ref>"
    },
    "name": "portal_invoice_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description correctly spends its words elsewhere: it discloses the not-found outcome for someone else's or unknown references (a scoping/security behavior) and that free text is wrapped as data (an injection-safety behavior). It also enumerates the returned content, which matters because there is no output schema. Not a 5 only because 'free text is wrapped as data' is stated without explaining what an agent should do with the wrapping.

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?

One dense sentence, front-loaded with the identity of the resource and the key, followed by the return contents and two edge-case notes. Every clause earns its place; the only cost is that the returned-field enumeration makes the sentence long and slightly list-like.

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

Completeness5/5

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

With one parameter, no output schema, and annotations covering the safety profile, the description supplies exactly the missing pieces: what 'ref' is, what comes back (lines, charges, discount, per-currency totals, payment stages, paid/remaining, bank account), and what happens on a miss. An agent has everything needed to call and interpret it correctly.

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?

Schema coverage is 0%, so the description must carry the parameter's meaning, and it does: the single 'ref' is the invoice number, with a concrete format example (CI-0001) that matches the schema's pattern. It does not explain the 3-24 character bound or the accepted character set, but the example conveys the practical format.

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?

States a specific verb and resource ('Details of one of your own commercial invoices') plus the addressing key ('by number, e.g. CI-0001'), which cleanly separates it from the list-style siblings. The scope word 'your own' also bounds what can be retrieved, so an agent knows exactly what this tool returns without opening a schema.

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?

Usage is implied rather than stated: fetch a single invoice when you already have its number. The description never says how to obtain a number (e.g. via portal_invoices_list) nor when to prefer the list/summary siblings instead. Adequate but leaves the routing decision to inference.

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