Skip to main content
Glama

White Automotive & Media Services Catalog

Get product

get_product
Read-onlyIdempotent

One product by SKU or URL slug: the search summary plus tags and attributes such as warranty, core charge and whether dealer service is required. Unknown identifiers return found:false. Never determines fitment: do not assert that a product fits a specific vehicle; send the customer to the product URL. UCP form: pass catalog.id. Example: {"identifier":"GMED-REPLACEMENTHMI"}

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "GMED-REPLACEMENTHMI"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaNoUCP form, optional. Any call with "catalog" or "meta" is UCP and returns structuredContent (prices in minor units).
catalogNoUCP form.
identifierNoSimple form, required. SKU or URL slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "identifier": "GMED-REPLACEMENTHMI"
      +  },
      +  {
      +    "catalog": {
      +      "id": "GMED-REPLACEMENTHMI"
      +    }
      +  }
      +]
    • changedInput schema / properties / catalog / description
      Previous value: -"UCP get_product request."New value: +"UCP form."
    • changedInput schema / properties / identifier / description
      Previous value: -"Product SKU or URL slug."New value: +"Simple form, required. SKU or URL slug."
    • changedInput schema / properties / meta / description
      Previous value: -"UCP request metadata. meta[\"ucp-agent\"].profile is the calling platform's profile URL (https)."New value: +"UCP form, optional. Any call with \"catalog\" or \"meta\" is UCP and returns structuredContent (prices in minor units)."
    • addedInput schema / properties / meta / properties / ucp-agent / properties / profile / description
      Added value: +"Your platform profile URL (https). Recorded, never fetched."
  2. Changed3 schema fields changed
    • addedInput schema / properties / catalog
      Added value: +{
      +  "description": "UCP get_product request.",
      +  "properties": {
      +    "id": {
      +      "description": "Product ID, SKU or URL slug.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / meta
      Added value: +{
      +  "description": "UCP request metadata. meta[\"ucp-agent\"].profile is the calling platform's profile URL (https).",
      +  "properties": {
      +    "ucp-agent": {
      +      "properties": {
      +        "profile": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "identifier"
      -]
  3. First observed

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/closed-world, and the description still adds substantive behavior: unknown identifiers return found:false, the UCP form returns structuredContent with prices in minor units, and the tool deliberately cannot answer fitment questions. The fitment prohibition is a real operational constraint that no annotation conveys.

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?

Front-loaded with the resource and return shape, then caveats, then the UCP instruction — a sensible order. It is dense and telegraphic with no filler, though the trailing example repeats what the schema already ships.

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?

For a three-parameter no-output-schema tool with nested UCP objects, it covers return content, the not-found case, the fitment limitation, and the dual call forms. Nothing an agent needs in order to call it correctly is missing.

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 baseline is 3, but the description adds the routing decision between the two call forms and explicitly says "UCP form: pass catalog.id," disambiguating a schema that lists no top-level required array. The inline example duplicates the schema's examples, so the gain is modest rather than full.

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?

States a specific verb and resource ("One product by SKU or URL slug") and enumerates the payload shape (search summary plus tags and attributes like warranty, core charge, dealer-service flag). An agent can tell this is a single-record fetch, distinct from the sibling search_catalog/lookup_catalog style operations, 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?

Clear context for use — you must already hold an identifier, and UCP callers pass catalog.id — plus an explicit negative rule ("Never determines fitment... send the customer to the product URL"). It does not name when to prefer lookup_catalog or search_catalog, so it stops short of full alternative routing.

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