Skip to main content
Glama

White Automotive & Media Services Catalog

Browse category or tag

lookup_catalog
Read-onlyIdempotent

List products in a category (GM platform or application) or tag (such as "global-a"). An unknown name is searched as words instead, and the result says so. Same shape as search_catalog. Never determines fitment: do not assert that a product fits a specific vehicle; send the customer to the product URL. UCP form: look up by catalog.ids. Example: {"tag":"global-a"}

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": {
      "tag": "global-a",
      "limit": 10
    },
    "name": "lookup_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoSimple form. Tag name or slug, e.g. "global-a", "vin-programmed".
metaNoUCP form, optional. Any call with "catalog" or "meta" is UCP and returns structuredContent (prices in minor units).
limitNoSimple form. Maximum results.
catalogNoUCP form. Unmatched ids are reported in not_found messages.
categoryNoSimple form. Category name or slug (GM platform or application). Give category, tag or both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 10,
      +    "tag": "global-a"
      +  },
      +  {
      +    "catalog": {
      +      "ids": [
      +        "GMED-REPLACEMENTHMI",
      +        "GMED-REPLACEMENTCSM"
      +      ]
      +    }
      +  }
      +]
    • changedInput schema / properties / catalog / description
      Previous value: -"UCP lookup request."New value: +"UCP form. Unmatched ids are reported in not_found messages."
    • changedInput schema / properties / category / description
      Previous value: -"Product category slug."New value: +"Simple form. Category name or slug (GM platform or application). Give category, tag or both."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return."New value: +"Simple form. Maximum results."
    • 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."
    • changedInput schema / properties / tag / description
      Previous value: -"Product tag slug."New value: +"Simple form. Tag name or slug, e.g. \"global-a\", \"vin-programmed\"."
  2. Changed2 schema fields changed
    • addedInput schema / properties / catalog
      Added value: +{
      +  "description": "UCP lookup request.",
      +  "properties": {
      +    "ids": {
      +      "description": "Product IDs, SKUs or URL slugs.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 20,
      +      "minItems": 1,
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "ids"
      +  ],
      +  "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"
      +}
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds substantive behavior: unknown names are silently reinterpreted as word searches and the result discloses that, UCP calls return structuredContent with prices in minor units, and unmatched ids surface as not_found messages.

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 listing behavior, then constraints, then the UCP form and example. Dense but each sentence carries information; the fitment warning and fallback note are both earning their place.

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?

Five parameters including a nested UCP object and no output schema, so the description needs to carry weight -- it explains the two call forms, the response shape by reference to search_catalog, and error reporting. Pagination/limit semantics are only covered by the schema, a minor gap.

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 the conceptual split between the simple form (category/tag) and the UCP form (catalog.ids) plus a worked example, which the schema's flat property list does not convey as clearly.

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: list products in a category (GM platform or application) or tag, with a concrete example tag. It names the two lookup modes and the UCP variant, but the distinction from search_catalog is only 'same shape as search_catalog', which describes the result rather than the purpose.

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

Usage Guidelines3/5

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

Gives a real constraint -- never assert fitment, send the customer to the product URL -- and notes the unknown-name fallback, which hints at when this tool is appropriate. It does not say when to prefer this over search_catalog or get_product, so sibling routing is left to inference.

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