Skip to main content
Glama

askr_set_policy

Publish or replace an Askr store policy (returns, shipping, warranty, FAQ) when the catalog key matches the store’s policy key, so the assistant can quote it to visitors.

Instructions

Publish or replace a policy (returns, shipping, warranty, FAQ) in the Askr store, if this agent's catalog key is the store's policy key. The store's assistant quotes it to visitors.

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": {
      "slug": "<slug>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "askr_set_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesPolicy text in markdown.
slugYesPolicy id, such as "returns" or "shipping".
titleYesPolicy title shown to visitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.61

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the operation overwrites an existing policy ('replace'), that it is gated on catalog-key ownership, and that the result becomes publicly quotable by the store assistant to visitors. It still omits error behavior (unknown slug, key mismatch), whether replacement is reversible, and what a successful call 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?

Two sentences, no filler, and the core action and its precondition are front-loaded before the downstream consequence. Every clause contributes: the action, the policy domains, the authorization gate, and the visitor-facing effect.

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 three-parameter write tool with 100% schema coverage and no output schema, the essentials are present, but the description never addresses failure modes or the relationship to preview/diff workflows. An agent could invoke it correctly but would be guessing about error handling and about whether a preview step is expected first.

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 slug, title, and body are already documented with formats and examples in the schema; the baseline of 3 applies. The description's parenthetical domain list loosely reinforces the slug vocabulary but adds nothing about body semantics or size limits beyond what the schema states.

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 uses a specific verb pair and resource — 'Publish or replace a policy' — and enumerates the policy domains (returns, shipping, warranty, FAQ), so the agent knows exactly what mutation is being performed. It does not name any sibling tool to contrast with (e.g. askr_upsert_products or askr_preview_diff), so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a real gating condition — 'if this agent's catalog key is the store's policy key' — which tells the agent when the call is legally permitted. However, it offers no guidance on when to write a policy versus previewing a change first, and askr_preview_diff is an obvious neighbor that goes unmentioned, leaving the alternative selection implicit.

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