Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set company tax exemption

set_company_tax_exemption
Destructive

Exempts a company record's orders from VAT by applying a legal reason, or clears the exemption with null. Requires customers:manage and site:config:edit.

Instructions

Exempt a company record's orders from VAT, or clear the exemption with null. An exempt company's carts and orders carry 0% and 0 tax with reason as the legal note, whatever its VAT id; in a workspace that stores gross prices the VAT inside them is removed, not charged. Carts already holding the old status are refused at checkout (BUYER_CHANGED) and orders keep the treatment they were placed with. Needs customers:manage and site:config:edit, the same pair as set_company_vat_verified 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>",
      "reason": "<reason>"
    },
    "name": "set_company_tax_exemption"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesThe legal basis of the exemption, printed on each of the company's orders (3-300 characters); null clears the exemption
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.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description goes far beyond them, disclosing the downstream effect (0% and 0 tax on carts and orders with the reason as legal note), gross-price workspace behavior where embedded VAT is removed rather than charged, that already-placed orders keep their original treatment, the required permission pair (customers:manage and site:config:edit), and the returned fields. This is unusually rich behavioral disclosure for a 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?

Front-loaded with the primary action and its reversal, then layered with consequences, permissions, and return shape. Sentences are dense and occasionally run long (the permission sentence in particular), but no sentence is filler.

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?

For a two-parameter mutation with no output schema, the description covers everything an agent needs: effect on existing data, edge-case refusal, permissions, preconditions, and return fields. Nothing material is missing.

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 coverage is 100%, so both parameters are already documented, including the null-clears behavior and 3-300 character limit. The description reinforces that reason becomes the legal note printed on orders and that recordId must belong to a Company-capability model, but adds little syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('Exempt a company record's orders from VAT') plus the inverse operation ('clear the exemption with null'), and explicitly contrasts with set_company_vat_verified by noting it shares the same permission pair. An agent can distinguish this from the other set_company_* siblings without opening schemas.

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?

Clear context for when to call it (exempt a company) and how to reverse it (null), plus explicit refusal conditions: non-company records are rejected, and carts holding the old status are refused at checkout with BUYER_CHANGED. It stops short of naming an alternative tool for VAT-id changes, so it is strong guidance without explicit exclusions.

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