Skip to main content
Glama

catalog_search

Search an indexed catalog of community reverse-engineering tools, MCP servers, and agent skills by query, category, type, or stars to find relevant resources.

Instructions

Search the indexed catalog of community reverse-engineering tools, MCP servers and agent skills.

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
typeNoall
limitNo
queryNoFree text, e.g. ghidra, android, firmware, unpacker, flutter, electron
categoryNoCategory substring filter, e.g. Mobile, Firmware, Debuggers
min_starsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 burden. It never states result format, how results are ordered or ranked, whether 'limit' truncates silently, or what min_stars=0 implies, leaving the agent without behavior context beyond the word 'search'.

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 zero filler; the resource and scope come first. Its brevity is efficient, though the same brevity contributes to the gaps scored elsewhere.

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?

A 5-parameter search tool with no annotations and no output schema needs the description to explain ranking, limit behavior, and return shape. Instead it offers only one sentence, so an agent cannot predict what a result looks like or how paging/truncation works.

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 40% - query and category have examples, but limit and min_stars are bare numbers with defaults and no explanation. The description adds no parameter meaning at all, so the undocumented half stays undocumented in both places.

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 ('Search') and a well-defined resource ('the indexed catalog of community reverse-engineering tools, MCP servers and agent skills'), which is clearer than a sibling like catalog_categories. It stops short of naming how it differs from catalog_categories or fetch_tool, so an agent must infer the division of labor.

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 mention of the alternatives in the sibling set (catalog_categories for browsing categories, fetch_tool for retrieving a specific entry). The agent has to guess whether search or category browsing is the intended entry point.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.