Skip to main content
Glama

Propose recording an invoice payment

invoices_collect

[Invoicing changes] Propose recording payments (incasare) on an issued invoice: bank order (Ordin de plata), receipt (Chitanta, needs receipt_series), card, cash, etc. One payment with type/value/date/document_number, or several in payments (for example several bank orders that paid one invoice); without value the whole invoice is collected. Refused when the payments exceed the invoice total: an advance larger than the invoice stays for the next invoice. Simulated first; nothing is recorded until the seller approves. Works on: Demo invoicing (sample 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": {
      "series": "<series>",
      "number": "<number>"
    },
    "name": "invoices_collect"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, the day the money arrived. Default: today.
typeNoDefault: Ordin de plata.
valueNoDefault: the invoice total.
numberYes
seriesYes
accountNoAccount id from list_accounts. Optional when only one account is connected.
mentionsNo
paymentsNoSeveral payments on the same invoice, instead of the single-payment fields.
receipt_seriesNoReceipt series, for type Chitanta.
document_numberNoBank order / payment document number (required unless type is Chitanta).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is partly covered. The description adds genuinely non-obvious behavior beyond that: dry-run-then-approve semantics, the over-payment rejection rule, carry-forward of advances, and the receipt_series requirement for Chitanta. This is solid added context, though it does not address idempotency/retry behavior despite idempotentHint=false.

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?

Front-loaded with the action and then the important modes (single vs multiple, over-payment, simulation). Dense but every sentence carries operational meaning; the parenthetical Romanian terms and the trailing environment note are the only mildly cluttering elements.

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?

For a 10-parameter mutation-like tool with an output schema, the description covers the critical decision points: simulation/approval, over-payment refusal, and the receipt_series dependency. Remaining gaps (account selection, idempotency on retry) are partly covered by the schema, so the definition is close to 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 70%, so the schema already carries most parameter meaning including defaults. The description adds useful semantics for two cases: omitting 'value' collects the whole invoice, and 'payments' is for several bank orders against one invoice. It does not clarify 'account', 'mentions', or the document_number requirement beyond what the schema states.

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 ('Propose recording payments (incasare) on an issued invoice') and enumerates the payment types covered (bank order, receipt, card, cash). It also distinguishes the single-payment and multi-payment shapes, so an agent can tell this apart from sibling read tools like invoices_get or invoices_list.

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?

Gives concrete operating context: it is simulated first, nothing is recorded until the seller approves, and it works only on 'Demo invoicing (sample data)'. It also states the rejection condition (payments exceeding the invoice total) and what happens to the excess. It does not name an alternative sibling for cases where the agent should read or cancel instead, so it stops short of explicit routing.

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