Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set company vat verified

set_company_vat_verified
Destructive

Attest or withdraw a company VAT id check to zero-rate its EU orders as reverse charge; withdrawing restores standard taxation. Requires a stored VAT id matching expectedVatId.

Instructions

Attest that a company record's VAT id was checked (for example in VIES), or withdraw that attestation. A verified EU VAT id of another member state than the workspace's sellerCountry (update_cart_config) zero-rates the company's orders as reverse charge, unless an order ships to the seller's country, or out of the EU as an export; withdrawing it taxes them as standard again. Carts already holding the old status are refused at checkout (BUYER_CHANGED) and orders keep the treatment they were placed with. Refused when the company has no VAT id (set it with set_company_vat_id) and with CONFLICT when the stored id differs from expectedVatId. Needs customers:manage and site:config:edit, the same pair as set_company_tax_exemption and as 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>",
      "verified": "<verified>"
    },
    "name": "set_company_vat_verified"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordIdYesThe company record's id (a record of a model with the Company capability; a customer's company.id)
verifiedYestrue attests the VAT id was checked, false withdraws it
expectedVatIdNoThe VAT id you checked, as get_record's vatId shows it; required to verify. A different stored id is refused with CONFLICT

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?

Beyond destructive=true and readOnly=false, it discloses reverse-charge tax effects, checkout refusal with BUYER_CHANGED, existing orders retaining their treatment, permission requirements, refusal conditions, and returned fields. This is rich context for a destructive mutation.

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 core action is front-loaded, followed by necessary consequences and prerequisites, and the density is appropriate for a destructive tax-status mutation. Some permission cross-reference wording is verbose, so it is not maximally concise.

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?

There is no output schema, but the description states the returned fields and covers permissions, side effects, refusal conditions, and order/cart behavior. That is complete for a tool of this complexity.

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 baseline is 3, but the description adds meaning by explaining the tax consequence of verified true versus false and the expectedVatId CONFLICT condition. It also reinforces that recordId must refer to a company record, though the schema already documents much of this.

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?

The first sentence states a precise action: attesting or withdrawing attestation that a company's VAT id was checked. It also distinguishes this from set_company_vat_id, which is named as the tool for setting the id, and scopes the target to a company record.

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?

It gives concrete use and withdrawal conditions via the verified boolean, refusal cases such as no VAT id, non-company records, and expectedVatId CONFLICT, and names set_company_vat_id as the prerequisite alternative. It also states the required permission pair, helping an agent judge feasibility before invoking.

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