mcp-server-smallinvoice

update_bank_account

Update bank account details such as name, number, IBAN, or BIC for an existing account in Smallinvoice.

Instructions

Updates specified bank account

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": {
      "account_id": "<account_id>"
    },
    "name": "update_bank_account"
  }
}

Input Schema

Name	Required	Description
`account_id`	Yes	account ID
`default`	No	whether it is a default bank account
`description`	No	description
`bank_name`	No	name of the bank
`number`	No	bank account number
`iban`	No	IBAN
`bic`	No	BIC
`post_account`	No	bank’s postal account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate it's a mutable non-destructive operation. The description does not add behavioral details like whether it's a partial update or full replacement, or any side effects.

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?

Single sentence, no unnecessary words. Efficient and to the point.

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?

Despite annotations, the description lacks completeness for a mutation tool with 8 parameters. No mention of update behavior (partial vs full), no output description. Leaves ambiguity for the agent.

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 descriptions cover 100% of parameters. The tool description adds no extra parameter meaning beyond the schema, so baseline 3 is appropriate.

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 'Updates specified bank account' clearly states the action and resource. It distinguishes from siblings like create_bank_account and delete_bank_accounts.

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

Usage Guidelines2/5

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

No guidance on when to use or when not to use. No mention of prerequisites or alternatives. The description only states what it does with no contextual cues.

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

Deploy Server