DigiSnap-MCP

compare_prices

Compare prices for multiple products across selected stores to identify the best deal. Supports backward-compatible price comparison using a canonical engine.

Instructions

Backward-compatible price comparison using the canonical comparison engine.

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": {
      "product_ids": "<product_ids>",
      "store_ids": "<store_ids>"
    },
    "name": "compare_prices"
  }
}

Input Schema

Name	Required	Description	Default
`store_ids`	Yes
`product_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 29, 2026

TDQS

D1.7/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no mutability, auth requirements, rate limits, or what the comparison returns. 'Backward-compatible' hints at deprecation status but is too vague to count as meaningful disclosure.

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

Conciseness3/5

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

The definition is a single short sentence with no padding, so it is not verbose. However, the brevity comes at the cost of substance — the one sentence is mostly jargon rather than front-loaded operational information.

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

Completeness1/5

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

For a tool with two required, completely undocumented parameters, no annotations, and no output schema, the description provides essentially no information an agent needs to invoke it correctly. It is inadequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both required parameters (product_ids, store_ids) have 0% schema description coverage, and the description says nothing about them — not their format, cardinality, or how they are matched. The description therefore fails to compensate for a complete schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'price comparison' essentially restates the tool name, and 'using the canonical comparison engine' / 'backward-compatible' are undefined jargon that add no operational meaning. It does not distinguish this tool from siblings like compare_products, compare_offers, or find_best_price, so an agent cannot tell what unique behavior it offers.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance. 'Backward-compatible' faintly implies a legacy alias that a newer tool supersedes, but it never names that alternative or states the condition under which an agent should pick this one over the several comparison siblings.

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

Deploy Server