RoboHub Robot Catalog

Search robots

search_robots

Search RoboHub's catalog of commercial robots by free-text query and optional filters. Returns compact summaries with catalog URLs. When max_price_usd is set: Only robots with a verified manufacturer list price (MSRP) at or below this USD amount; estimates and quote-only robots are excluded.

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": "search_robots"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results to return (default 10, max 25).
`query`	No	Free-text search over name, manufacturer, category, use cases and description (e.g. 'warehouse pallet AMR', 'quadruped inspection').
`category`	No	Restrict to one category.
`max_price_usd`	No	Only robots with a verified manufacturer list price (MSRP) at or below this USD amount; estimates and quote-only robots are excluded

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / max_price_usd / description

Previous value: -"Only robots with a known price at or below this USD amount."New value: +"Only robots with a verified manufacturer list price (MSRP) at or below this USD amount; estimates and quote-only robots are excluded"

First observedJun 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the return format ('compact summaries with catalog URLs') and a meaningful filtering caveat about verified MSRP. However, the MSRP text is duplicated verbatim from the schema, and there is no mention of permissions, rate limits, or pagination behavior.

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?

Front-loaded with the core action in the first sentence, followed by return format and the price constraint. Three tight sentences; the only minor redundancy is restating the max_price_usd rule already in the schema.

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?

No output schema exists, and the description compensates by describing the returned summaries and catalog URLs. For a four-parameter read tool with fully documented params, this is reasonably complete, missing only tie-breaking guidance against siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters, establishing a baseline of 3. The description largely repeats the max_price_usd semantics rather than adding syntax or format meaning beyond the schema.

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 and resource: 'Search RoboHub's catalog of commercial robots by free-text query and optional filters.' This is clear and identifiable, though it does not explicitly name how it differs from siblings like get_robot or list_categories.

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

Usage Guidelines3/5

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

Usage is implied by 'by free-text query and optional filters' and the price-scoping rule, but there is no explicit when-to-use guidance or routing to alternatives such as get_robot for a specific robot. Adequate but with a clear gap.

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

All RoboHub Robot Catalog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?