Skip to main content
Glama

save_store_shipping_rate

Destructive

Create or edit a store shipping rate. Use revision 0 to create, or the current revision to edit. Money amounts are in minor units of the store currency.

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": {
      "id": "<id>",
      "name": "<name>",
      "countries": "<countries>",
      "amount": "<amount>",
      "currency": "<currency>",
      "revision": "<revision>"
    },
    "name": "save_store_shipping_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYes
activeNo
amountYes
currencyYes
revisionYes
countriesYes
freeAboveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but say nothing about how mutation is gated; the description adds the revision-based optimistic-concurrency contract, which is genuine behavioral disclosure beyond the annotations. It omits what happens on a stale-revision conflict and whether an edit fully replaces the rate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, then the create/edit rule, then the currency-unit caveat. No filler or restatement of the title.

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?

No output schema, so callers get no guidance on what a successful save returns, and there is no mention of conflict/validation failure behavior. For a destructive 8-parameter mutation with 0% schema coverage, the description covers the highest-risk spots but leaves meaningful gaps.

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 0% across 8 parameters, so the description must carry the load; it usefully explains `revision` semantics and that `amount`/`freeAbove` are minor units of the store currency. It leaves `countries`, `active`, `name`, and the 3-letter currency code format unexplained.

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?

"Create or edit a store shipping rate" gives a specific verb pair and resource, and no sibling in the catalog targets shipping rates, so an agent can route to it unambiguously. It stops just short of explicitly differentiating itself from the other save_* tools.

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?

The description gives real selection logic for the create-vs-edit fork: "Use revision 0 to create, or the current revision to edit." It does not name alternatives (e.g. a read/get tool that supplies the current revision), so the caller must infer where the current revision value comes from.

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