Skip to main content
Glama

list_invoices

Retrieve invoices, including previously paid ones, and filter by purchase order, status, or vendor to review accounts-payable records.

Instructions

Invoices in the system, including ones paid in earlier periods.

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

Input Schema

NameRequiredDescriptionDefault
po_idNo
statusNo
vendor_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about read-only vs mutation semantics, pagination, result volume, sorting, or default filters. The only behavioral disclosure is that invoices paid in earlier periods are included, which is a genuine scoping fact but far from sufficient.

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

Conciseness2/5

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

It is only one fragment, but the brevity reflects under-specification rather than economy. There is no front-loaded statement of what the tool does, so the single sentence conveys almost no actionable structure.

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

Completeness1/5

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

With three undocumented parameters, no annotations, and no output schema, the definition should explain filtering behavior and return shape; it does neither. An agent has essentially only the tool name to work from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters (po_id, vendor_id, status) have 0% schema description coverage, and the description mentions none of them. An agent cannot learn from this text how to filter by purchase order, vendor, or status, nor what the enum values mean in combination.

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

Purpose2/5

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

The description is a noun phrase ('Invoices in the system') rather than a verb+resource statement, so it only restates what the name list_invoices already conveys. The one added detail — that results include invoices paid in earlier periods — hints at scope but doesn't establish whether this is a list/search/export operation or how it differs from get_invoice or list_pos.

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 when-to-use guidance, no statement of when not to use it, and no pointer to alternatives such as get_invoice for a single record or list_pos for purchase orders. The implicit hint that paid invoices from prior periods are included is the only clue an agent gets about selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.