Skip to main content
Glama

Get product passport

get_passport
Read-only

A product passport: the brand's own listing, then every other store found carrying it, each marked same item, likely same, other version, bundle or accessory, with the evidence for that call. This is the only place a reseller is identified rather than guessed. Examples: "is this seller an authorized reseller", "which stores carry the exact same jacket".

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_url": "<product_url>"
    },
    "name": "get_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_urlYesA product_url from search_products

Output Schema

NameRequiredDescriptionDefault
reasonNo
productNo
passport_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product_url / description
      Previous value: -"Shopify product URL (seller_url)"New value: +"A product_url from search_products"
  2. Changed2 schema fields changed
    • changedInput schema / properties / product_url / description
      Previous value: -"A Shopify product URL (from search_products seller_url), from the brand or any reseller."New value: +"Shopify product URL (seller_url)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "passport_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "product": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral detail about the output taxonomy (same item, likely same, other version, bundle, accessory, each with evidence), but says nothing about latency, coverage limits, or what happens when no other store is found; the output schema carries the rest.

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?

Three compact sentences with the output content front-loaded and the examples last; nothing is wasted. The opening fragment is slightly awkward and would read better with an explicit verb, but the density is good.

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?

With one documented parameter and an output schema, the definition only needs to convey purpose and selection cues, which it largely does through the classification vocabulary and example queries. The main residual gap is routing relative to sibling tools that also touch product/store data.

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 coverage is 100% and the single parameter is already documented as "A product_url from search_products", including its provenance. The description adds no further constraint or format guidance beyond what the schema supplies, so the baseline of 3 applies.

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?

The description states concretely what the tool returns: the brand's own listing plus every other store carrying the item, each tagged with a match classification and supporting evidence. That is far more specific than the title, though the first sentence is a verbless fragment ("A product passport: ...") and it never explicitly contrasts itself with get_product or compare_prices.

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?

Two concrete example questions ("is this seller an authorized reseller", "which stores carry the exact same jacket") give a clear sense of when to reach for this tool, and the line about being the only place a reseller is identified rather than guessed signals its unique role. There are no explicit exclusions or named alternatives for overlapping cases like price comparison.

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