Skip to main content
Glama

settings_tax_rates

Set or remove the tax rate for a place. Money is integer minor units (cents). Calling this changes nothing: it returns a preview of what would change and a confirmation link. Only the merchant, on that page, can make it happen.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoWhat it is called on the order: "Irish VAT", "NY sales tax". Required for a new rate; up to 60 characters.
actionYesset: add a rate for the place, or change the one already there (only the fields given move). remove: delete the place's rate.
countryYesISO 3166-1 alpha-2, like PT or US. Empty or * is the catch-all for anywhere not named by another rate.
rateBpsNoThe rate in basis points: 23% is 2300, 8.875% is 888. Required for a new rate.
provinceNoState, county or region inside the country, as the checkout address spells it (CA, Dublin). Empty or * is the whole country.
isEnabledNoWhether the rate is applied at all; off keeps it in the list without charging it. New rates default to true.
appliesToShippingNoWhether the rate is charged on the delivery line as well as the goods. New rates default to true, the EU way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior1/5

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

The annotations declare readOnlyHint=false, but the description says 'Calling this changes nothing' and that only the merchant can make the change happen. That directly contradicts the annotation and makes the tool's actual mutation behavior confusing.

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 front-loaded and compact, using three short sentences. The money-integer-minor-units sentence is slightly disconnected from the actual schema parameters, keeping it from being perfectly economical.

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?

It gives the essential workflow context, including the preview and confirmation-link behavior, and the schema covers all parameters. However, the contradiction with the readOnlyHint annotation leaves the tool's side effects ambiguous, and no output schema exists to clarify the returned preview.

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 100%, so the schema already documents all seven parameters thoroughly. The description adds a general note about money being integer minor units, but it does not add parameter-specific meaning beyond the schema.

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?

The description states a specific verb and resource: set or remove the tax rate for a place. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling settings_tax tool.

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?

It provides clear operational context: calling it changes nothing, returns a preview and confirmation link, and only the merchant can complete the action. It does not explicitly name alternatives or when-not-to-use conditions, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources