Skip to main content
Glama

Delete non-receipt payment

delete_payment
DestructiveIdempotent

Remove a card payment, bank transfer, or promissory note that has no receipt number. Use when a payment was recorded with wrong amount or client, or never arrived.

Instructions

Remove a collection that has no receipt number of its own — a card payment, bank transfer, promissory note and so on. Irreversible.

Use this to undo a create_payment that recorded the wrong amount, the wrong client or a payment that never arrived. Because these payments have no series and number, identify one either by the invoice it settles (invoiceNumber, plus invoiceSeries) — which is the reliable way — or, if it is not tied to an invoice, by paymentDate and paymentValue together with the client.

For receipts (chitanta), use cancel_payment or delete_receipt instead. Confirm with the user first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientCifNoClient CIF. Not needed when the invoice is known.
clientNameNoClient name. Not needed when the invoice is known.
paymentDateNoPayment date (YYYY-MM-DD). Not needed when the invoice is known.
paymentTypeYesType of the payment to delete.
paymentValueNoPayment amount. Not needed when the invoice is known.
invoiceNumberNoNumber of the settled invoice.
invoiceSeriesNoSeries of the settled invoice.
companyVatCodeNoIssuing company CIF. Falls back to SMARTBILL_VAT_CODE.
Behavior5/5

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

Description explicitly states 'Irreversible', aligning with destructiveHint=true. Adds behavioral context about undoing create_payment and identification strategies beyond annotations.

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?

Well-structured: definition, consequence, usage scenarios, alternatives. All sentences are informative; no fluff. Slightly long but fully justified.

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?

Complete for a delete tool with 8 params and no output schema. Covers identification, prerequisites, irreversibility, and sibling differentiation.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). Description adds value by clarifying which parameters are needed when (e.g., clientCif not needed if invoice known) and how to identify a payment.

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?

Clearly states the tool removes non-receipt payments (card, bank transfer, etc.) and explicitly distinguishes from receipt-related siblings.

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?

Provides explicit when-to-use (undo wrong payments), when-not-to-use (receipts use cancel_payment/delete_receipt), and identification methods. Also advises confirming with user.

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/bogdanripa/smartbill-mcp'

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