Skip to main content
Glama

Save a proposed settings change

apply_store_settings
Destructive

Saves a change proposed with its token, exactly as proposed, through the dashboard's own checks. Shoppers see it within 5 minutes. Recorded in the store's activity log with the app's name; every owner of the store gets an email with the change and a link that undoes it for 7 days. Refused when the token expired or the settings changed since. Needs the settings permission.

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": {
      "change_token": "<change_token>"
    },
    "name": "apply_store_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
change_tokenYesThe token of the proposed change.

Output Schema

NameRequiredDescriptionDefault
noteNo
savedYes
changesYes
store_idYes
owners_emailedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations by disclosing propagation latency (shoppers see it within 5 minutes), audit logging, and the owner-wide email with a 7-day undo link — information that materially changes how an agent should treat a destructive call. It also names the failure modes and the required permission, so the destructiveHint and openWorldHint annotations are backed by concrete consequences.

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?

Five short sentences, each carrying a distinct fact: application semantics, propagation, audit/notification, refusal conditions, permission. Front-loaded with the core action and no filler text.

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 single-parameter destructive write with an output schema already covering the return value, the description supplies everything else an agent needs: prerequisites, side effects, reversibility window, and error conditions. Nothing material is missing.

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 real meaning about the token itself — that it is single-purpose, tied to a specific proposal, expires, and is rejected if the underlying settings moved. That makes the parameter's lifecycle clear beyond the one-line schema description.

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 ('Saves a change proposed with its token') and pins down the scope with 'exactly as proposed', which implicitly separates it from the proposal-creating sibling. An agent can tell this is the apply step rather than the propose step without opening the schema.

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?

Gives clear preconditions — a token from a prior proposal, the settings permission — and states the two refusal cases (expired token, settings changed since). It does not explicitly name propose_store_settings as the prerequisite source of the token, so the routing guidance is strong but not fully spelled out.

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