Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set company vat id

set_company_vat_id
Destructive

Set or clear a company's EU VAT ID with automatic normalization and format validation; malformed IDs are refused, and changed IDs require re-verification before VAT-exempt order taxation.

Instructions

Set the EU VAT id of a company record. cmssy normalizes it (spaces, dots and dashes dropped, GR read as EL) and checks it against the member state's format; a malformed id is refused (BAD_USER_INPUT). null or empty clears it. A changed id is no longer verified, so its orders are taxed as standard until set_company_vat_verified attests the new value. Needs customers:manage. Verifying the id or exempting the company (set_company_vat_verified, set_company_tax_exemption) needs customers:manage and site:config:edit, and so does linking a customer to a company whose VAT id is verified or that is tax exempt. Refused for a record that is not a company (a model with the Company capability). Returns the record id with vatId, vatCountry, vatVerifiedAt, vatVerifiedBy and taxExemptReason.

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": {
      "recordId": "<recordId>",
      "vatId": "<vatId>"
    },
    "name": "set_company_vat_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
vatIdYesThe EU VAT id with its country prefix, e.g. DE123456789; null or empty clears it
recordIdYesThe company record's id (a record of a model with the Company capability; a customer's company.id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: VAT id normalization rules, member-state format validation, BAD_USER_INPUT refusal, clearing semantics, unverification after change, tax impact, permissions, and refusal for non-company records. This is consistent with destructiveHint=true because the operation can clear or invalidate a previously verified id.

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 dense and front-loads the operation, but it is long and packs permissions, sibling tools, tax consequences, and return fields into one block. Most sentences earn their place, though it could be structured more cleanly for scanning.

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

Completeness5/5

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

Given no output schema, the description explains the returned fields, and it covers permissions, validation, clearing, tax consequences, and sibling-tool relationships. An agent has enough information to invoke this mutation correctly and understand the main risks.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters, but the description adds meaningful semantics about vatId normalization and null/empty clearing. It also clarifies that recordId must refer to a model with the Company capability, beyond the schema wording.

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?

States a specific verb and resource: setting the EU VAT id of a company record. It clearly distinguishes this mutation from verification by naming set_company_vat_verified and explaining that a changed id is no longer verified.

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

Usage Guidelines5/5

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

Explicitly covers when to use it, how null/empty clears the value, malformed input refusal, permission requirements, and the related alternative operations set_company_vat_verified and set_company_tax_exemption. It also explains the consequence of changing an id: orders are taxed as standard until verification.

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

Deploy Server

Other Tools