Skip to main content
Glama

askr_preview_diff

Compares your product list with the current Askr store catalog and reports which items a sync would create, update, or hide without publishing changes.

Instructions

Compare products with what the Askr store lists now and report what a sync would create, update and (with replace=true) hide. Publishes nothing.

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": {
      "products": "<products>"
    },
    "name": "askr_preview_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
replaceNotrue: `products` is the whole catalog, and every listed product missing from it would be hidden (a call takes at most 200 products, so a larger catalog cannot be previewed as a replace). false: only these products are compared.
productsYesProducts, at most 200 per call. Each: d (the product id, unique in the store), title, price {amount as a decimal string, currency}, and optionally summary, description, images (https), url (the product page, https, on one of the store origins or link origins, else not shown), topics, attrs, options, variants, visibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.61

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden and does so: it asserts nothing is published, and it discloses the consequential side of replace=true (unlisted products would be hidden). It does not cover return shape, scale limits, or auth requirements, so there are gaps for a no-annotation tool.

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, zero filler, and the core promise (compare + report) is front-loaded before the non-mutation caveat. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Against a deeply nested product schema, a preview tool, and no output schema, the description gives the agent enough to know what question the tool answers and that it is safe. What the report actually looks like (field names, whether diffs are per-product, truncation behavior) is left unspecified, which is the main residual gap.

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% and the replace parameter is already documented in detail in the schema, including the 200-product ceiling. The description's '(with replace=true) hide' only restates what the schema says, adding no new syntax or behavioral detail for parameters.

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 (compare products against the current Askr store listing) and enumerates the outcome categories (create, update, hide). 'Publishes nothing' cleanly separates it from the mutating sync siblings such as askr_upsert_products or askr_hide_products.

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 comparison framing plus 'Publishes nothing' tells an agent this is the dry-run step before a real sync, and the replace=true note flags when the comparison is catalog-wide. It never explicitly names askr_upsert_products/askr_hide_products as the follow-up, so the routing is implied rather than stated.

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