Skip to main content
Glama

cyanheads-mcp-server

by io.github.cyanheads

Search Fleet Tools and Servers

cyanheads_search_catalog
Read-only

Search fleet tools and servers by natural-language description. Returns ranked matches with brief summaries and the server each tool belongs to. Use scope "servers" to find which server handles a workflow; use the default scope "tools" to find specific tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-20). Default 5.
queryYesNatural language search query. Describe what you want to accomplish, a workflow, or a capability area. 1-500 characters.
scopeNoWhat to search. "tools" returns individual tool matches; "servers" returns server-level matches.tools
categoryNoFilter by catalog category. Omit to search all categories.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
scopeNoScope that was searched.
noticeNoGuidance when no results matched — e.g. how to broaden the query or try a different scope. Absent on successful result pages.
resultsNoRanked matches, best first.
serversNoRoll-up of distinct servers across the full match set, before the limit slice. Present only for scope "tools". Ordered by topScore desc (name-tiebroken); capped at 10. Use serversTotal to see how many distinct servers matched in total.
totalCountNoTotal relevant matches before the limit was applied.
serversTotalNoTotal distinct servers in the full match set (before the cap of 10 is applied). Present only when servers is present.
effectiveQueryNoThe query that was searched.

TDQS

A4.4/5.0
Behavior4/5

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

The annotation readOnlyHint=true already discloses the read-only nature,REDUCING the burden. The description adds concrete behavior: returns ranked matches, includes summaries, and reports which server each tool belongs to. It also defines what the two scopes return. No contradiction with annotations. Not perfect because it doesn't hint at result limits or staleness, but the added value is solid.

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?

Two sentences, front-loaded with purpose and key output featuresasi. The scope guidance is placed in the second sentence and earns its place. No filler or repetition of schema content.

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?

The description gives enough for an agent to properly invoke the tool: it explains the two scopes)Skip, notes ranked results with summaries, and the output schema (marked present) covers return structure. The 'category' parameter is not mentioned but is self-explanatory in the schema, and the tool's moderate complexity doesn't require more.

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?

With 100% schema coverage, the baseline is 3. The description compensates by adding meaning to the 'scope' parameter (choose 'servers' for workflows, 'tools' for specifics), which is genuinely useful beyond the schema text. Other parameters (query, limit, category) are adequately covered by their schema descriptions, so no further elaboration needed.

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 opens with the verb 'Search' and the specific resource 'fleet tools and servers', immediately stating what it does. It also disambiguates from the sibling cyanheads_describe_entry by emphasizing natural-language description and ranked matches, making the purpose unmistakable.

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 gives explicit guidance on when to use each scope: 'use scope "servers" to find which server handles a workflow; use default "tools" to find specific tools.' This tells the agent exactly how to select scope. It doesn't explicitly state when NOT to use the tool (e.g., when you need full details of a known entry, use describe_entry), but the clear scope disambiguation compensates.

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

All cyanheads-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool serves a distinct function: one retrieves detailed information about a specific known entry, the other performs broad searches across the catalog. They are complementary with no overlap in purpose.

Naming Consistency5/5

Both tools follow the same verb_noun pattern with the 'cyanheads_' prefix (describe_entry, search_catalog). The naming is perfectly consistent and predictable.

Tool Count4/5

The server exposes only 2 tools, which is slightly thin but appropriate for its narrow purpose of discovery. Two tools fully cover the describe-and-search workflow without redundancy.

Completeness5/5

The search and describe tools together form a complete discovery workflow: agents can search to find tools/servers, then describe to get installation and usage details. No functional gaps exist for the stated purpose.

Resources