Skip to main content
Glama
ERP Procurement MCP Server

ERP Procurement MCP Server

Search invoices

search_invoices
Read-only

Lists supplier invoices from the ERP ordered by due date, with filters for status, supplier, and due date so you can find invoices to review before payment.

Instructions

Lists supplier invoices from the ERP, soonest due first. Filter by status, supplier (id or part of the name) and due date. Use it to find invoices to check before payment.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-50
offsetNoNumber of results to skip
statusNoOnly invoices with this status
supplierNoSupplier id (SUP-001) or part of the supplier name
dueBeforeNoOnly invoices due on or before this date (YYYY-MM-DD)

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value with the ERP source and default ordering (soonest due first), but says nothing about result volume, pagination behavior, or truncation despite a very large offset maximum in the schema.

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?

Three short, front-loaded sentences: what it does, what can be filtered, and when to reach for it. Minor filler exists ('from the ERP') but nothing is redundant or bloated.

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?

Output schema exists, so return values need not be described, and every filter is either in the schema or the text. The only gap is absent guidance on paging through large result sets, which is a small omission for a read-only search tool.

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 description coverage is 100%, so all five parameters are already documented, including the supplier id-or-name convention and dueBefore format. The description restates the same three filters without adding syntax or edge-case meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ('Lists supplier invoices from the ERP') plus a scope detail ('soonest due first'). The list verb contrasts implicitly with the single-record sibling get_invoice, but no sibling is named, so differentiation is left partly to inference.

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

Usage Guidelines4/5

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

'Use it to find invoices to check before payment' gives a clear use context, which distinguishes it from approval-oriented siblings like request_approval. It stops short of explicit when-not-to-use conditions or naming an alternative search path.

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