Skip to main content
Glama

Filter the catalogue

lookup_catalog
Read-only

Preferred structured discovery. Filter by category, partial colour name or required supported width/drop in mm. Returns results containing product_id, name, category and product_url, plus total. Width/drop filters check separate maximums, not every combination; confirm the exact pair with 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": "lookup_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
colourNo
categoryNoroller | venetian | honeycomb | vertical | outdoor
max_width_mmNo
max_height_mmNo

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower, and the description clears it by disclosing a non-obvious behavior: width/drop filters are evaluated as independent maximums rather than intersecting every combination. That caveat materially changes how an agent should interpret results and is not derivable from the annotations or schema.

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 sentences, each carrying distinct load: positioning, filterable fields, return shape, then the caveat and handoff. The most important constraint is front-loaded in sentence one and the trap is flagged last, with no filler wording.

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?

An output schema exists, so restating product_id/name/category/product_url/total is mild redundancy rather than a gap. Combined with the independent-maximum caveat and the get_price handoff, an agent has everything needed to call this correctly for a four-parameter, zero-required filter 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 only 25% (category alone is documented), so the description must compensate, and it does: 'partial colour name' reveals substring matching for colour, and 'width/drop in mm' fixes the unit and physical meaning of max_width_mm and max_height_mm. It still never explicitly maps 'drop' to max_height_mm, leaving that inference to the reader.

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 first two sentences give a specific verb and resource ('Filter the catalogue') and enumerate the exact filter dimensions (category, partial colour, width/drop in mm), then state what comes back. 'Preferred structured discovery' implicitly separates it from the keyword-style sibling search_catalog, so an agent can pick between them without opening schemas.

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 a positive routing rule ('Preferred structured discovery') and an explicit follow-up handoff ('confirm the exact pair with get_price'). It does not state when this tool is the wrong choice — e.g. free-text or vague queries that would belong to search_catalog — so usage guidance is clear but not exhaustive.

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