Skip to main content
Glama

save_store_settings

Destructive

Save the store name, currency and publication setting. Use revision 0 for a new store or the saved revision from list_store_catalogue. Ask the owner to approve any change to public availability.

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": {
      "published": "<published>",
      "name": "<name>",
      "currency": "<currency>",
      "revision": "<revision>"
    },
    "name": "save_store_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
currencyYes
revisionYes
publishedYes

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 already declare destructiveHint=true and idempotentHint=false, so the description correctly adds context beyond them: the revision mechanism signals optimistic concurrency (stale revisions presumably rejected) and the owner-approval rule for public availability changes is a real behavioral constraint an agent must know. It stops short of stating what happens on a revision mismatch or what the response returns.

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, each earning its place: the action, the revision rule, and the approval constraint. The core operation is front-loaded with zero filler.

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?

For a destructive mutation with no output schema and no schema descriptions, the description covers the two non-obvious parameters well and flags the approval requirement. It is still thin on what a save overwrites, what a stale revision yields, and the expected currency format, which matters given the zero-coverage schema.

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 0% for all four required parameters, so the description carries the burden. It explains revision semantics (0 for new, saved value from list_store_catalogue) and clarifies that published controls public availability, but name and currency get no format or constraint detail, leaving half the parameters documented only by their identifiers.

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 opens with a specific verb plus resource ("Save the store name, currency and publication setting") and enumerates the fields being written. It does not explicitly distinguish itself from sibling savers like save_business_brand or save_store_shipping_rate, but the store-settings scope is unambiguous.

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 gives concrete operational guidance: use revision 0 for creation, or the saved revision obtained from list_store_catalogue, and require owner approval before changing public availability. It lacks explicit when-not-to-use conditions, but the create-vs-update routing and the approval prerequisite cover the main decision points.

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