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

update_payment

Update an existing payment while preserving unspecified fields by merging your changes with the current payment data.

Instructions

Update an existing payment. IMPORTANT: Holded's PUT /payments/{id} REPLACES the record rather than merging, so any field omitted from the body is blanked. To prevent that, this tool first re-reads the current payment and merges your changes over it, preserving fields you did not pass (contactId, bankId, date, ...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoPayment date as a Unix timestamp (seconds)
daysNoDays until due
nameNoPayment method name
amountNoPayment amount
bankIdNoBank account id to link the payment to
contactIdNoContact id associated with the payment
paymentIdYesPayment ID to update
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the underlying API does full replacement, but this tool merges changes. This is key behavioral insight. Could add more like authorization needs.

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?

Two sentences: first states purpose, second explains the important behavioral note. No wasted words, front-loaded, and easy to parse.

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

Completeness3/5

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

The description covers input behavior well but does not mention return values. Since there is no output schema, the agent might need to know what the tool returns (e.g., the updated payment object).

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%, so individual parameters are documented. The description adds value by explaining the overall merge behavior, which clarifies how parameters interact and why omitted fields are preserved.

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 states 'Update an existing payment' with a specific verb and resource. It clearly distinguishes from sibling tools like create_payment and delete_payment by focusing on the update action.

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?

The description explains the critical behavior of read-merge-update, which guides when to use this tool (to update with partial fields without blanking omitted ones). It does not explicitly mention when not to use, but the context is clear.

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