Get full details for one specific AI tool by its slug — includes features, pricing, agenticness scores, and structured attributes. Use this when you know the exact tool slug. To find a slug, use search_listings first. For comparing two tools, use compare_listings. Note: null on boolean fields means 'unknown', false means 'confirmed no'.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The listing slug (e.g. 'cursor', 'claude-code', 'openclaw') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but the description adds crucial behavioral context beyond schema: explains that null on boolean fields means 'unknown' while false means 'confirmed no'. This is valuable for interpreting results. Lacks mention of any side effects, but as a read-only lookup this is acceptable.
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?
Three concise sentences front-loaded with purpose, then usage guidance, then a note on boolean semantics. No fluff.
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 simple retrieval tool with one required parameter and no output schema, the description sufficiently explains what it returns and provides a key nuance about null/false. Could be slightly more explicit about the output format (single object) but overall adequate.
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?
Schema description coverage is 100% with a clear description of the slug parameter. The tool description does not add additional semantic detail beyond what the schema already provides, so baseline of 3 is appropriate.
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?
The description clearly states the tool retrieves full details for one specific AI tool by slug, explicitly mentioning included fields (features, pricing, agenticness scores, structured attributes). It differentiates from siblings like compare_listings and search_listings.
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?
Provides explicit when-to-use (when slug is known), when-not-to (need slug first), and alternatives (search_listings to find slug, compare_listings for comparison). Perfect guidance.
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 has a clearly distinct purpose, with descriptions explicitly guiding when to use each. Overlaps between search/recommend tools are resolved by detailed usage instructions (e.g., recommend_tools vs semantic_search vs search_listings).
All tool names use consistent snake_case and follow a verb_noun pattern (e.g., compare_listings, get_category, search_listings). Even semantic_search, while adjective_noun, matches the style seamlessly.
10 tools is ideal for a directory server: covers discovery, search, comparison, and detailed analysis without being overwhelming. Each tool serves a clear role in the workflow.
Covers core directory operations (browse, search, filter, compare, details). Lacks a 'list all tools' function, but users can retrieve listings per category or via search. Minor gap, but overall sufficient for agents.
