Skip to main content
Glama

catalog_search

The whole catalog in one place: every service with its price, and every item you can buy (concepts of all 7 collections, journeys, archetypes, chakras, stones). Filter with type, collection, q (free). Free.

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": "catalog_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to match in titles and summaries
langNoLanguage of the core texts (default it)
typeNo
limitNo
offsetNo
collectionNoCollection id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only partially succeeds: it discloses that results include prices and cover all seven collections, journeys, archetypes, chakras and stones. It says nothing about pagination behavior, default or maximum result counts despite limit/offset parameters, result ordering, or authentication/licensing constraints behind the repeated 'Free' claim, which is itself ambiguous.

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?

It is a single compact sentence with the resource front-loaded, and the parenthetical efficiently enumerates scope. However, the repeated trailing 'Free.' is noise and the 'q (free)' phrasing is confusing, so it is not entirely waste-free.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, no-annotation, no-output-schema tool, the definition is thin: it omits pagination semantics and result-size expectations that the limit/offset parameters make essential, and leaves the return shape largely to inference. The purpose is conveyed but not enough to invoke the tool confidently at scale.

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 coverage is 50%, and the schema already documents q, lang and collection. The description names type, collection and q, which is largely redundant with the schema and adds no syntax or value meaning; the parenthetical enumeration hints at what type values represent but does not map them to the enum. The undocumented limit and offset parameters are not addressed at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this is a catalog-wide listing of services with prices and buyable items spanning concepts, journeys, archetypes, chakras and stones, which is more concrete than the bare name. But it frames the tool as a commercial catalog ('every item you can buy'), which blurs the line against siblings like library_concepts, library_search, chakra_list and stone_list without ever naming which to prefer. The verb is also ambiguous between listing and searching.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no exclusion conditions, and never names an alternative tool despite many overlapping siblings (library_search, library_concepts, stone_list). The only guidance is 'Filter with type, collection, q', which is invocation mechanics rather than tool selection.

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