Skip to main content
Glama

Search the blinds catalogue

search_catalog
Read-only

Preferred free-text discovery. Returns results containing product_id, name, category, description, product_url and colour_count_in_stock, plus total and currency. For structured filters use lookup_catalog. Pass product_id to get_product or get_price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text query, e.g. 'blockout' or 'venetian'

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the description only needs to add workflow context — which it does by describing the result payload and the follow-up calls that consume product_id. It leaves out result limits/pagination and empty-result behavior, which is the main remaining gap.

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 short sentences, front-loaded with the primary routing fact and then the payload and follow-ups. The field enumeration is somewhat redundant given an output schema exists, but it is compact enough not to be noise.

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?

For a one-parameter search with annotations and an output schema, this covers selection, usage, and next steps. It stops short only on result thriftiness — no mention of how many results come back or what an empty match looks like.

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?

The single query parameter is fully documented in the schema, including examples ('blockout', 'venetian'). The description reinforces that it is free-text rather than structured, but adds no syntax, multi-term, or matching-behavior detail beyond that baseline.

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?

The description states a specific mode (free-text discovery) on a specific resource (the blinds catalogue) and enumerates the result fields, so an agent knows exactly what it returns. It also distinguishes itself from lookup_catalog, which handles structured filters.

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?

It states when to use it ('Preferred free-text discovery'), when to use the alternative ('For structured filters use lookup_catalog'), and what to do next with the returned IDs ('Pass product_id to get_product or get_price'). No inference is required.

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