Skip to main content
Glama
nubiia-dev
by nubiia-dev

pay_document

Register a payment for a document, which auto-approves it. Optionally link the payment to a bank account using bankId.

Instructions

Register a payment for a document. IMPORTANT: this AUTO-APPROVES the document as a side effect (status 0→1) — Holded has no separate approve endpoint, and approval cannot be undone via the API. paymentmethod is the payment-method catalog id (from list_payment_methods), NOT a bank/treasury id. To link the payment to a bank account, pass bankId: the /pay endpoint can't set it, so the tool performs a second step (PUT /payments/{id}) and reports the outcome in _warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoPayment date as Unix timestamp
amountYesPayment amount
bankIdNoBank account id to link the payment to. Triggers a second step (PUT /payments/{id}) because /pay cannot set the bank link.
docTypeYesType of document
documentIdYesDocument ID
treasuryIdNoTreasury account ID
paymentmethodNoPayment-method catalog id (from list_payment_methods), NOT a bank/treasury id.
Behavior5/5

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

Discloses the auto-approval side effect, the irreversibility of approval via API, and the second-step process for linking a bank account. No annotations are provided, so the description carries the full burden and does so comprehensively.

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?

Two sentences, but the second is quite long. Still, it front-loads the purpose and crucial warning. Could be slightly more structured but remains concise and informative.

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

Completeness5/5

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

Given the complexity (7 parameters, side effects, no output schema), the description covers all critical aspects: side-effect, parameter clarification, workflow, and warnings. It is fully complete for an agent to use correctly.

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

Parameters5/5

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

Adds meaning beyond the schema by explaining that paymentmethod is a catalog id from list_payment_methods, not a bank/treasury id, and that bankId triggers a PUT step reported in _warnings. Schema coverage is 100% but the description still adds valuable context.

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 'Register a payment for a document,' which is a specific verb+resource. It distinguishes from siblings like create_payment and update_payment by emphasizing the side effect of auto-approval.

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

Usage Guidelines5/5

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

Explicitly warns about auto-approving the document and that approval cannot be undone. Clarifies that paymentmethod is a catalog id and bankId triggers a second step, providing guidance on when to use each parameter.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nubiia-dev/mcp-holded'

If you have feedback or need assistance with the MCP directory API, please join our Discord server