Skip to main content
Glama

search_catalog

Read-only

Find tools and skills by name, task or task tag.

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
qNo
tagNo
kindNo
sortNo
viewNo
limitNoResults per page. Default: 5.
cursorNoPass the previous next_cursor back unchanged.

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes
contributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false) and open-endedness, so the bar is lower. The description adds one genuine behavioral detail: matching happens against name, task, and task tag, which is the same field `q` left undocumented in the schema. It says nothing about pagination, result ordering (relevance vs github_stars), or result volume, which matter for a paged search endpoint.

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?

A single front-loaded sentence with no filler, and the three search dimensions are packed in efficiently. Its terseness is a symptom of missing content rather than padding, so it scores well here but is not exemplary.

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 7-parameter paged search with sort modes, a view mode, a kind enumeration, and a cursor, a ten-word description is too thin; an output schema means return values need not be explained, but pagination, sort semantics, and sibling differentiation are absent. Combined with low schema coverage, an agent cannot confidently compose calls beyond a bare `q`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29%; only `limit` and `cursor` carry descriptions, leaving `q`, `tag`, `kind`, `sort`, and `view` undocumented. The description partially compensates for `q` by naming the matched fields, but it introduces ambiguity with the `tag` parameter by saying "task tag" without clarifying whether the free-text query hits tags or whether the `tag` filter must be used separately. No explanation of `kind` enumeration, `sort`, or `view` behavior is offered.

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 ("Find") and resource ("tools and skills") plus the three matching dimensions (name, task, task tag), so the agent knows what kind of lookup this is. It does not, however, distinguish itself from catalog siblings such as search_topics, get_catalog_facets or get_catalog_item, so an agent comparing near-names must open the schemas to tell them apart.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. Given siblings like get_catalog_facets (browsing) and get_catalog_item (fetch by id), the description should say when a free-text/name search is preferable, but it leaves that entirely 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