Skip to main content
Glama

Find invoices

mercoa_find_invoices
Read-only

Find/search invoices (bills) across payers and vendors. Filter by status, entity, date, approver and more. GET /invoices (plural list endpoint).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax invoices to return (1-100, default 10).
searchNoSearch by vendor name, invoice number, check number, or amount.
statusNoInvoice status filter (e.g. DRAFT, NEW, APPROVED, SCHEDULED, PAID).
endDateNoEnd date filter (ISO 8601).
orderByNoField to order by (e.g. CREATED_AT, AMOUNT, DUE_DATE).
payerIdNoFilter by payer ID(s) or foreign ID(s).
dateTypeNoDate type to filter by (e.g. CREATED_AT, DUE_DATE).
entityIdNoFilter by entity (payer or vendor) ID(s) or foreign ID(s).
vendorIdNoFilter by vendor ID(s) or foreign ID(s).
invoiceIdNoFilter by invoice ID(s) or foreign ID(s).
startDateNoStart date filter (ISO 8601).
approverIdNoFilter by assigned approver user ID(s).
paymentTypeNoFilter by payment type (e.g. recurring).
creatorUserIdNoFilter by the user ID(s) that created the invoice.
entityGroupIdNoFilter by entity group ID.
startingAfterNoInvoice ID cursor for pagination.
approverActionNoFilter by approver action (use with approverId), e.g. APPROVE.
orderDirectionNoasc or desc.
invoiceTemplateIdNoFilter by invoice template ID(s).
returnPayerMetadataNoInclude payer metadata in the response.
returnPaymentTimingNoInclude payment timing in the response.
returnVendorMetadataNoInclude vendor metadata in the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, so the description does not need to repeat it. It adds context about being a list endpoint, which implies pagination. However, it does not disclose rate limits, pagination behavior, or response structure beyond what annotations and schema provide. With annotations covering the safety profile, a score of 3 is appropriate.

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

Conciseness5/5

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

The description is a single sentence plus a parenthetical about the endpoint. It is concise, front-loaded with the key purpose, and contains no unnecessary words.

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?

Given 22 optional parameters, no output schema, and readOnlyHint annotation, the description adequately covers the tool's purpose and filter capabilities. It could be improved by mentioning pagination or the default return format, but it is still mostly complete.

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 22 parameters are well-described in the schema. The description only lists filter types generically, adding no new meaning beyond the schema. Baseline is 3.

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 clearly states it finds/searches invoices (bills) across payers and vendors, lists several filter types, and explicitly mentions the endpoint 'GET /invoices (plural list endpoint)'. This distinguishes it from sibling tools like mercoa_get_invoice (singular) and mercoa_create_invoice.

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?

The description implies when to use the tool (search/filter invoices) but does not explicitly state when not to use it or provide alternatives like mercoa_get_invoice for a single invoice. The endpoint hint gives some context, but clearer guidance would improve the score.

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.