mcp-server-smallinvoice

create_bank_account

Add a new bank account to your Smallinvoice profile by providing a description and IBAN. Optionally include bank name, account number, BIC, and postal account.

Instructions

Creates new 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": {
      "description": "<description>",
      "iban": "<iban>"
    },
    "name": "create_bank_account"
  }
}

Input Schema

Name	Required	Description
`default`	No	whether it is a default bank account - default value: false
`description`	Yes	description
`bank_name`	No	name of the bank
`number`	No	bank account number
`iban`	Yes	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.1/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, which tell the agent this is a write operation and not destructive. The description adds no extra behavioral context, but it does not contradict the annotations. It is adequate given the 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?

The description is extremely concise, consisting of only four words. While it is front-loaded and efficient, it could be slightly expanded with no extra fluff, but it earns its place by stating the core function.

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?

Given 7 parameters and no output schema, the description should provide more context about what happens after creation (e.g., returns the created account). It is incomplete for an AI agent to fully understand the tool's behavior.

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?

The input schema has 100% description coverage for its 7 parameters. The description 'Creates new bank account' does not add any additional meaning beyond what the schema provides, so it meets the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Creates new bank account', which specifies the action (creates) and the resource (bank account). However, it does not differentiate from other creation tools for different resources, but the name itself is specific, so no strong need for further differentiation.

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 is provided on when to use this tool versus alternatives (e.g., update_bank_account) or when not to use it. The description lacks context on prerequisites or typical scenarios.

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

Deploy Server