Skip to main content
Glama

Relatie opslaan

save_contact
Destructive

Create or update a customer record for invoicing, capturing required name and address plus VAT and country details for Dutch and EU tax compliance.

Instructions

Create a customer (omit id) or update one (pass id). Name and address are required on an invoice. vat_id is required to invoice an EU business with btw verlegd. country is an ISO code such as NL, BE, DE, US.

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": "save_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
cityNo
nameNo
emailNo
vat_idNo
countryNo
kvk_numberNo
postal_codeNo
address_lineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/overwrite nature is covered structurally. The description adds business rules about invoicing requirements, which is real value, but never says that updating an existing contact overwrites current field values or whether changes are reversible. Given the annotation coverage, a 3 is fair.

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?

Four short sentences with the create/update rule front-loaded and no filler. The 'required on an invoice' phrasing is slightly ambiguous about whether it is a hard validation or an implied rule, which keeps it from a 5.

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?

For a 9-parameter mutation with no output schema, the definition covers the key decision and the two main business constraints, but leaves three parameters undocumented and says nothing about what is returned. Adequate minimum rather than complete.

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 0%, so the description must carry the semantics, and it only partly does: it explains id, name, address, vat_id, and country. email, kvk_number, and the split between address_line, postal_code, and city are left entirely to the reader. Useful but incomplete compensation.

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?

States a specific verb and resource plus the create-vs-update duality: 'Create a customer (omit id) or update one (pass id).' That is more precise than the title alone. It does not name a sibling such as find_contacts, so it stops short of a 5.

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?

Gives an explicit selection rule for its own two modes (omit id to create, pass id to update) and states the business conditions under which fields become mandatory (name/address for invoicing, vat_id for EU btw verlegd). It offers no exclusions or routing to alternatives like find_contacts.

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