Skip to main content
Glama

Verify Compared Offer

compare_verify_offer
Read-onlyIdempotent

Verify a single compared marketplace offer by fetching its source-native product card, confirming raw price, stock and seller, and checking expected identity, price or variant when supplied.

Instructions

Verify one compared offer through its marketplace card tool.

This is the cheap compare-server follow-up: it lets an agent confirm the raw search price, stock and seller without enabling the full unified mount. The returned card is source-native and therefore keeps fields the comparison intentionally normalises away.

Full field list and error codes: guide://compare/compare_verify_offer.

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": {
      "source": "<source>",
      "product_id_or_url": "<product_id_or_url>"
    },
    "name": "compare_verify_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesMarketplace source name from compare_prices, e.g. wildberries or ozon.
expected_identityNoOptional manufacturer identifiers and variant attributes to verify against the card.
product_id_or_urlYesproduct_id or direct product URL from the compared offer
expected_price_rubNoPrice returned by compare_prices; used to report a live card delta.
expected_variant_idNoYandex variant_id from the search row; rejects a different card SKU.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.0
    • addedInput schema / properties / expected_identity
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "Product-family/variant evidence, independent of a seller offer.",
      +      "properties": {
      +        "brand": {
      +          "default": "",
      +          "type": "string"
      +        },
      +        "gtin": {
      +          "default": "",
      +          "type": "string"
      +        },
      +        "model": {
      +          "default": "",
      +          "type": "string"
      +        },
      +        "mpn": {
      +          "default": "",
      +          "type": "string"
      +        },
      +        "native_product_id": {
      +          "default": "",
      +          "type": "string"
      +        },
      +        "source": {
      +          "default": "",
      +          "type": "string"
      +        },
      +        "variant_attributes": {
      +          "additionalProperties": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional manufacturer identifiers and variant attributes to verify against the card."
      +}
    • addedInput schema / properties / expected_variant_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 100,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Yandex variant_id from the search row; rejects a different card SKU."
      +}
  2. Addedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile needs no restating. The description does add real value by disclosing that the returned card is source-native and therefore retains fields the comparison normalises away, plus that this path is 'cheap'. It stops short of describing failure behaviour or rate/latency costs, deferring those to the guide resource.

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

Conciseness4/5

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

Four short sentences with the action front-loaded first and operational context after; nothing is padded. The phrase 'full unified mount' is under-defined jargon that costs a little clarity without adding length.

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?

An output schema exists, annotations cover the safety profile, and parameters are fully described, so the description's modest scope is largely justified. It correctly points to `guide://compare/compare_verify_offer` for the full field list and error codes, covering the remaining gap, though it never states what a verification mismatch means for the caller.

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 every parameter including the expected_identity object and expected_price_rub delta reporting is already documented in structured form. The description adds only loose narrative context ('raw search price, stock and seller') that maps to existing schema fields rather than extending their meaning, so the baseline 3 holds.

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 verb and resource ('Verify one compared offer') and explains the mechanism ('through its marketplace card tool'), so the agent knows this resolves a single offer to its source-native card. It does not name a specific sibling it competes with, referring instead to the vague 'full unified mount', so differentiation is only partial.

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?

Clearly frames the tool as the cheap compare-server follow-up used to confirm raw search price, stock and seller, which tells the agent when to reach for it. It implies an alternative path ('without enabling the full unified mount') but never names that alternative tool or states explicit exclusions.

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