Revuo

categories.list

Read-only

Lists all product categories in the directory. Use category slugs to filter product searches in products.search / products.find_by_capability. Response: { categories: [{ slug, name, description }] }. Note: this is a thin call. For a full directory briefing (subcategories, capability slugs per category, product counts, locked-vertical flags), prefer directory.overview as a single up-front call.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`categories`	No

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds behavioral context: it's a 'thin call' and specifies the response structure with fields slug, name, description. It does not contradict annotations.

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?

The description is three sentences, front-loaded with the main action, and every sentence adds value: purpose, relationship to other tools, response format. No redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter tool, the description covers all needed context: what it does, output format, and how to use results. Output schema exists externally, so no need to detail return values further.

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?

The input schema has no parameters, so schema coverage is 100% (vacuously). The description adds no parameter info but explains the response shape. With zero parameters, baseline is 4.

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 clearly states the verb 'lists' and the resource 'product categories', and explicitly mentions using the returned slugs for filtering in products.search and products.find_by_capability. It distinguishes itself from sibling tool directory.overview by noting it's a 'thin call'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises when to use this tool (for a thin list) and when to prefer directory.overview (for a full briefing). It also indicates the use of slugs for subsequent product searches.

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

All Revuo tools Inspect

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.4/5.0

Disambiguation4/5

The namespace grouping separates products, tools, taxonomy, and rankings cleanly, and each tool's description points to its intended query mode. Some overlap exists between products.search and products.find_by_capability, and between tools.search and tools.find_for_task, but the descriptions are detailed enough that an agent can usually pick correctly. categories.list and directory.overview also overlap, though directory.overview is explicitly marked as the preferred entry-point.

Naming Consistency4/5

The set follows a predictable `resource.action` dotted convention, with all-lowercase names and snake_case within actions. Minor deviations such as `directory.overview`, `tools.changes`, and `mcp.score_server` mix noun actions and verb+object phrases, but the overall pattern remains readable and easy to guess.

Tool Count4/5

14 tools is appropriate for a read-only directory covering products, capabilities, rankings, MCP setup, and tool discovery. The count is slightly high because the search/find family has several close variants, but each variant has a distinct query style and use case.

Completeness5/5

The surface covers the domain thoroughly: taxonomy, product search and details, capability lookup, agent-readiness scoring, rankings, MCP setup, tool discovery, and schema-drift detection. Cross-references such as products.get_mcp_setup supplying the hash consumed by tools.changes close the main workflow loops without dead ends.

Resources

Need Help?