mcp-server-smallinvoice

list_invoice_payments

Read-only

Retrieve all payments recorded for a specific invoice, enabling payment tracking and reconciliation.

Instructions

Returns list of payments for specified invoice

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "list_invoice_payments"
  }
}

Input Schema

Name	Required	Description
`invoice_id`	Yes	invoice ID
`with`	No	Comma separated, optional keys that should be included in the response.
`q`	No	Value for full text search
`filter`	No	Filter expression (JSON)
`limit`	No	Limits the number of items returned. Number in a range [1-200]
`offset`	No	Offset of the first item to return. The offset of the initial item is 0.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read. The description adds no new behavioral traits beyond that. It does not discuss pagination, result format, or ordering, but with annotations covering the basic safety profile, a 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.

Conciseness4/5

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

The description is a single sentence of six words, front-loaded with the verb 'Returns'. It contains no wasted words. However, it could be slightly expanded to include key details like pagination support without becoming verbose.

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

Completeness2/5

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

For a list tool with 6 parameters (including optional filters, search, pagination) and no output schema, the description is too minimal. It does not explain the return format, hint at filtering or search capabilities, or mention pagination behavior. Given the complexity, the description leaves significant gaps.

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 each parameter already has a description in the schema. The tool description does not add any additional meaning to the parameters beyond the schema. Baseline 3 is correct when schema does the heavy lifting.

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 'Returns list of payments for specified invoice' clearly states the verb (returns), resource (list of payments), and scope (for specified invoice). It distinguishes from sibling tools like get_invoice_payment (singular) and list_invoices (different entity).

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?

No explicit when-to-use or when-not-to-use guidance is provided. The purpose implies using it to list payments for an invoice, but alternatives like get_invoice_payment or record_invoice_payment are not mentioned. Usage context is implied but not stated.

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

Deploy Server