Skip to main content
Glama

Get indexed product details

get_product
Read-onlyIdempotent

Use this after global_search when the selected candidate needs indexed details that are not already on its search card. The p2209_id must come from global_search. This remains a snapshot, not live merchant verification; follow the returned handoff before confirming variant, price, or stock. Skip this call when the search card already answers the question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
p2209_idYesKaliCart product ID (e.g. prod_duinshop-it_432395)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
errorNo
priceNo
scopeNo
handoffNo
categoryNo
p2209_idYes
variantsNo
attributesNo
provenanceNo
updated_atNo
merchant_idNo
product_urlNo
availabilityNo
storefront_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "attributes": {},
      +    "availability": {},
      +    "category": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "handoff": {},
      +    "merchant_id": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "p2209_id": {
      +      "type": "string"
      +    },
      +    "price": {},
      +    "product_url": {
      +      "anyOf": [
      +        {
      +          "format": "uri",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "provenance": {},
      +    "scope": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "type": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "type"
      +      ],
      +      "type": "object"
      +    },
      +    "storefront_url": {
      +      "anyOf": [
      +        {
      +          "format": "uri",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "updated_at": {
      +      "anyOf": [
      +        {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "format": "date-time",
      +              "type": "string"
      +            }
      +          ]
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "variants": {}
      +  },
      +  "required": [
      +    "p2209_id"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds material behavioral context: this is a snapshot, not live merchant verification, and the returned handoff must be followed before confirming variant, price, or stock. That staleness/handoff disclosure is exactly the kind of trait an agent needs and cannot get from structured fields.

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?

Three tight sentences, front-loaded with the trigger condition before the ID provenance rule and the skip condition. No redundant restatement of the name or schema.

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?

With an output schema present, the description needn't explain return values, and it covers the remaining gaps an agent needs: prerequisite source of the ID, the snapshot limitation, the handoff requirement, and when to skip. Nothing essential is missing for a 1-parameter read tool.

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% and the single parameter is fully documented in the schema, so baseline would be 3. The description adds provenance semantics beyond the schema: p2209_id must originate from global_search, which is a real constraint on how to obtain a valid value.

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 ('get product' returning indexed details) and explicitly positions itself against the sibling global_search. The scope is clear, though it does not enumerate what 'indexed details' comprises beyond the caveat that it is a snapshot rather than live merchant data.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('after global_search when the selected candidate needs indexed details not already on its search card') and when-not-to-use ('skip this call when the search card already answers the question'), plus the prerequisite that p2209_id must come from global_search. Alternatives and exclusions are fully covered.

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.