mcp-server-smallinvoice

update_contact_address

Update a contact's address by specifying contact and address IDs. Optionally provide fields such as street, city, country, and default status.

Instructions

Updates specified address

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": {
      "contact_id": "<contact_id>",
      "address_id": "<address_id>"
    },
    "name": "update_contact_address"
  }
}

Input Schema

Name	Required	Description
`contact_id`	Yes	contact ID
`address_id`	Yes	address ID
`default`	No	whether it is a default contact's address
`country`	No	country ISO2 code (eg. CH)
`street`	No	street
`street_no`	No	number of apartment
`street2`	No	additional address information
`postcode`	No	postcode
`city`	No	city
`hide_on_documents`	No	whether to hide this address on documents
`default_prepage`	No	whether the address is a default postal address

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 indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral details beyond the action itself. It does not disclose whether only provided fields are updated or if other fields are affected. With annotations present, the description meets a minimal threshold but adds little value.

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 very concise with a single sentence. While it could benefit from a bit more detail, it is not verbose and is front-loaded with the core purpose.

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 the tool has 11 parameters and no output schema, the description is insufficient. It does not explain the return value, error conditions, or the behavior for optional parameters (e.g., whether fields are partially updated). The openWorldHint annotation suggests unspecified side effects, yet the description lacks context.

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 description coverage is 100%, so the input schema already documents all parameters. The description does not add any further meaning to the parameters, maintaining the baseline score of 3.

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 'Updates specified address' clearly indicates the action and resource, but does not explicitly mention that it is a contact address. However, the tool name and parameters make it reasonably clear, and it distinguishes from sibling update tools for other entities.

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?

The description provides no guidance on when to use this tool versus alternatives like create_contact_address, delete_contact_addresses, or get_contact_address. No context on prerequisites or when not to use it.

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

Deploy Server