RoboHub Robot Catalog

Compare two robots

compare_robots

Side-by-side spec comparison of two robots by slug, plus RoboHub's editorial verdict when available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug_a": "<slug_a>",
      "slug_b": "<slug_b>"
    },
    "name": "compare_robots"
  }
}

Input Schema

Name	Required	Description	Default
`slug_a`	Yes	First robot slug.
`slug_b`	Yes	Second robot slug.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations exist; description implies read-only behavior by stating comparison. However, does not explicitly disclose non-destructive nature or any constraints like rate limits or permissions.

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?

Single, concise sentence with no wasted words. Front-loads the core action and includes a relevant extra detail.

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

Completeness3/5

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

For a simple tool with two parameters and no output schema, description covers basic purpose but lacks detail on return format or what 'specs' means. Adequate but could be more complete.

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 already fully describes parameters (slug_a, slug_b) with 'First/Second robot slug.' Description adds 'by slug' which is consistent but does not enhance meaning beyond schema.

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?

Description clearly states verb 'compare', resource 'two robots', method 'by slug', and additional output 'editorial verdict'. Distinguishes from sibling tools that handle single robots or search.

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?

Implies use for comparing two known robots by slug, but no explicit when-to-use or alternatives listed. Sibling names are provided but not referenced.

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?