Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

Verify a live Shopify offer (Seller Agent)

verify_agent_offer
Read-only

Verify the current price and availability of a product sold by a Shopify store that enabled MagicGEO Seller Agent. Facts are read live from the merchant's Shopify Admin at call time. Without variant_id, returns the product's variants with their state. With variant_id, returns state (VERIFIED, OUT_OF_STOCK or UNAVAILABLE), the offer facts, a short-lived Ed25519-signed passport (verify with jwks_url) and, when VERIFIED, a native Shopify checkout URL for one unit. Stock is never reserved; final price, taxes, shipping and payment are decided by Shopify checkout. Product IDs are listed in the store's agents.md.

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": {
      "shop": "<shop>",
      "product_id": "<product_id>"
    },
    "name": "verify_agent_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopYesStore domain, e.g. example.myshopify.com
product_idYesNumeric Shopify product ID
variant_idNoNumeric Shopify variant ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld/idempotent, while the description adds substantial behavior: facts are read live at call time, stock is never reserved, and final price, taxes, shipping and payment are settled by Shopify checkout. It also discloses the signed passport mechanism and that it is short-lived and verifiable via jwks_url — none of which appears in the annotations.

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?

Front-loaded with the purpose, then conditional return behavior, then the commercial caveats, then the discovery pointer to agents.md. Every sentence carries distinct information; nothing is repeated from the schema or annotations.

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

Completeness5/5

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

No output schema exists, so the description carries the burden of describing returns and it does: variant states, VERIFIED/OUT_OF_STOCK/UNAVAILABLE, offer facts, passport, and a single-unit checkout URL. Caveats about non-reservation and checkout-final pricing close the remaining ambiguity for an agent acting on the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema cannot express: variant_id acts as a mode switch that changes both the return shape and whether a checkout URL is produced. It does not add format or syntax detail beyond the schema, which is fine given the patterns are already documented.

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?

Specific verb+resource ('Verify the current price and availability of a product sold by a Shopify store') with the data source named ('read live from the merchant's Shopify Admin'). It also splits the response shape by the presence or absence of variant_id, which lets an agent understand the tool's two modes without opening the schema.

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 description gives clear conditional usage rules: omit variant_id to enumerate variants, supply variant_id to get a verified offer and checkout URL, and it points to agents.md as the source of valid product IDs. What it lacks is any routing away from siblings (e.g. why not search_catalog first), so it stops short of explicit alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources