DigiSnap-MCP

analyze_offers

Expose observed discount, availability, warranty, and seller signals for specified products and stores without ranking offers, helping you inspect raw offer data for comparison.

Instructions

Expose observed discount, availability, warranty and seller signals without ranking.

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": "analyze_offers"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 29, 2026

TDQS

C2.7/5.0

Behavior2/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. It discloses only that the tool does not rank, but says nothing about read-only behavior, permissions, rate limits, or whether it mutates any state.

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 description is a single, front-loaded sentence with no wasted words. However, its extreme brevity leaves it under-specified for a tool with no annotations and undocumented parameters.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. Still, with no annotations, 0% parameter description coverage, and only minimal usage guidance, the description is not complete enough for an agent to invoke the tool confidently.

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?

Schema description coverage is 0%, and the description does not mention product_ids or store_ids at all. Both required parameters are left completely unexplained beyond their bare names in the input schema.

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?

States a specific action ('Expose') and enumerates the signal types observed (discount, availability, warranty, seller). The phrase 'without ranking' distinguishes it from ranking-oriented siblings like find_best_price and find_best_value, though it does not name them.

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?

The phrase 'without ranking' implies the tool is for raw signal inspection rather than ranked recommendations, which gives some usage context. However, it does not explicitly state when to use this tool instead of compare_offers, compare_prices, or find_best_value.

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

Deploy Server