list_collectionsThe curated buyer-intent collections (e.g. mcp-servers, testing-qa, browser-automation). Use get_collection for the ranked tools inside one.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, but description adequately describes a read-only listing operation. Provides examples and context about collections.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences that efficiently convey purpose and usage. No unnecessary content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, no-output-schema tool, description fully covers what the tool does and how it relates to sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters, so schema covarge is 100%. Description adds context about what is listed without needing parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it lists curated buyer-intent collections, with examples. Distinguishes from sibling get_collection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells when to use (list collections) and when not (use get_collection for tools inside one). Provides clear alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation: comparing tools, demand signals, collection details, single tool profile, listing collections, and searching. No functional overlap.
Five tools follow verb_noun pattern (compare_tools, get_collection, get_skill, list_collections, search_skills); demand_pulse is a noun phrase but remains clear. Minor deviation but consistent style.
Six tools is well-scoped for a read-only directory server: core operations (search, list, detail, compare, trends) are covered without bloat.
The tool surface covers all essential query operations: search, list collections, get tool details, compare tools, and demand data. No obvious gaps for its purpose.