Skip to main content
Glama

Bedrijfsgegevens

setup_business
Destructive

Create or update the Dutch business profile so invoice details, IBAN, btw-id and KOR dates stay correct. Pass only the fields that change.

Instructions

Create or update the business profile. Only pass fields that change. Name, address, KvK-nummer, IBAN and (unless the KOR applies) btw-id are legally required on invoices. kor_since is the first day of the kleineondernemersregeling (omit when the business charges btw); kor_until is the last day it applied, set only when the owner left the KOR. Neither may change how documents already booked are treated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "setup_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
ibanNo
nameNo
emailNoShown on invoices; receives a copy of every sent invoice
vat_idNo
kor_sinceNo
kor_untilNo
kvk_numberNo
owner_nameNo
vat_periodNoHow often the Belastingdienst wants a btw-aangifte; quarter is the default
postal_codeNo
address_lineNo
archive_emailNoMailbox that receives receipts as its archive; defaults to email
payment_term_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, destructive, closed-world mutation, so the base burden is lower. The description adds real context beyond that: partial-update merge semantics and the reassurance that KOR date edits do not retroactively change already-booked documents. It still does not say what a destructive update overwrites, whether previously issued invoices keep old data, or what the call returns.

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?

Three front-loaded sentences with no filler: purpose first, then the partial-update rule, then domain-critical legality and KOR semantics. The KOR clauses are dense but each carries decision-relevant information; slightly tighter phrasing around the two KOR fields would help scanning.

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

Completeness4/5

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

For a 14-parameter destructive upsert with no output schema, the description covers the highest-risk semantics (partial updates, legal requirements, KOR date handling, non-retroactivity), which is close to sufficient. Gaps remain around first-creation behavior and the untouched numeric/enum parameters, but the critical decisions an agent must get right are supported.

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?

With only 21% schema description coverage across 14 parameters, the description must compensate, and it partly does: it explains kor_since, kor_until, and names which data (name, address, KvK-nummer, IBAN, btw-id) is legally required, which ties to the empty required list. However, it never clarifies owner_name, payment_term_days, vat_period, or which field supplies the address (address_line vs. postal_code vs. city), leaving several parameters undocumented in both places.

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?

"Create or update the business profile" gives a specific verb pair (upsert) and resource, with no sibling in the catalog competing for that job. The upsert nature is stated up front, so an agent knows a single call handles both first-time setup and later edits.

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?

"Only pass fields that change" tells the agent to send partial payloads rather than a full object, and the KOR sentences give explicit conditional rules (omit kor_since when the business charges btw; set kor_until only after leaving the KOR). What is missing is any guidance on when in a workflow this should be called or what preconditions exist before first setup.

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