Skip to main content
Glama

White Automotive & Media Services Catalog

Search catalog

search_catalog
Read-onlyIdempotent

Free-text search of the White Automotive & Media Services GM electronics catalog. Returns name, SKU, price, availability, categories and URL per match; with no exact match, returns the closest and says so. Never determines fitment: do not assert that a product fits a specific vehicle; send the customer to the product URL. UCP form: inputs under "catalog". Example: {"query":"HMI module"}

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": {
      "limit": 5,
      "query": "HMI module"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaNoUCP form, optional. Any call with "catalog" or "meta" is UCP and returns structuredContent (prices in minor units).
limitNoSimple form. Maximum results.
queryNoSimple form, required. Product type, model or platform, e.g. "digital cluster Silverado". Synonyms work ("screen", "gauges").
catalogNoUCP form. Needs query, filters.categories or both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 5,
      +    "query": "HMI module"
      +  },
      +  {
      +    "catalog": {
      +      "pagination": {
      +        "limit": 5
      +      },
      +      "query": "digital cluster"
      +    }
      +  }
      +]
    • changedInput schema / properties / catalog / description
      Previous value: -"UCP search request. Needs query, filters.categories, or both."New value: +"UCP form. Needs query, filters.categories or both."
    • addedInput schema / properties / catalog / properties / filters / properties / categories / description
      Added value: +"Category names or slugs."
    • addedInput schema / properties / catalog / properties / pagination / description
      Added value: +"Pass the previous response cursor for the next page."
    • addedInput schema / properties / catalog / properties / query / description
      Added value: +"Search words."
    • 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 / query / description
      Previous value: -"Search terms. Maximum 120 characters."New value: +"Simple form, required. Product type, model or platform, e.g. \"digital cluster Silverado\". Synonyms work (\"screen\", \"gauges\")."
  2. Changed3 schema fields changed
    • addedInput schema / properties / catalog
      Added value: +{
      +  "description": "UCP search request. Needs query, filters.categories, or both.",
      +  "properties": {
      +    "filters": {
      +      "properties": {
      +        "categories": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "price": {
      +          "description": "min and max in minor units (cents).",
      +          "properties": {
      +            "max": {
      +              "minimum": 0,
      +              "type": "integer"
      +            },
      +            "min": {
      +              "minimum": 0,
      +              "type": "integer"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "pagination": {
      +      "properties": {
      +        "cursor": {
      +          "type": "string"
      +        },
      +        "limit": {
      +          "minimum": 1,
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "query": {
      +      "type": "string"
      +    }
      +  },
      +  "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: -[
      -  "query"
      -]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive, closed-world), the description discloses the exact return fields, the closest-match fallback with an explicit notice, and a hard safety constraint that it never determines fitment. That fitment restriction is a behavioral trait an agent could not derive from schema or annotations and directly prevents an unsafe assertion.

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 purpose, then return shape, then the fitment caveat and the form hint. Each sentence carries content; the trailing example partly duplicates the schema's examples array, which costs a little tightness.

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?

There is no output schema, and the description compensates by enumerating returned fields and describing the degraded-match case. Given the complexity of two input forms and a nested catalog object, it is nearly complete; only cursor/pagination behavior is left unmentioned in prose.

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 description coverage is 100%, so the schema already carries the parameter semantics, including the dual simple/UCP forms and the nested catalog object. The description's 'UCP form: inputs under "catalog"' line and the example largely restate what the schema and its examples already provide, adding only mild calling-convention emphasis.

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 gives a specific verb and resource: 'Free-text search of the White Automotive & Media Services GM electronics catalog.' The 'free-text' qualifier implicitly distinguishes it from an exact/keyed lookup, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

It states the search context (product type, model or platform, synonyms work) and a fallback rule for no exact match, which tells the agent how results behave. It stops short of explicit when-to-use/when-not routing against lookup_catalog or get_product for exact SKU or ID retrieval.

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