RoboHub Robot Catalog

Request vendor introductions

request_vendor_intros

Submit a B2B sourcing request to RoboHub on behalf of the user. Within 48 hours RoboHub replies by email with a free shortlist of 2-4 matching robots, indicative pricing and warm vendor introductions. Vendor-neutral and free for buyers. Only call this with the user's explicit consent and their real contact details.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Work email address where the shortlist should be sent.
`notes`	No	Anything else relevant (optional).
`company`	Yes	Company name.
`country`	No	Country of deployment (optional).
`industry`	Yes	Industry, e.g. 'logistics', 'agriculture', 'security', 'hospitality'.
`timeline`	Yes	Deployment timeline.
`use_case`	Yes	What the robots should do, with as much operational detail as possible (environment, scale, constraints).
`robot_slug`	No	Slug of a specific robot the user is interested in (optional).
`budget_range`	Yes	Approximate budget bracket in USD.
`contact_name`	Yes	Full name of the contact person.

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description fully carries the transparency burden. It discloses response timeline (48 hours), delivery method (email), output content (shortlist of 2-4 robots, pricing, warm intros), and neutrality/free nature. Missing details about error handling or failure modes, but overall adequate.

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 four sentences, front-loaded with the main action, and every sentence adds value. It is highly concise with no wasted words.

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?

Given the tool has 10 parameters and no output schema, the description covers the essential behavioral context: what happens after submission, timeline, and key constraints. It does not detail error states or full process, but is complete enough for selection and invocation.

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 baseline is 3. The description adds overall behavioral context but does not elaborate on individual parameters beyond what the schema provides. It mentions 'real contact details' but that is general guidance.

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 tool submits a B2B sourcing request to RoboHub on behalf of the user. It uses specific verb+resource ('Submit a B2B sourcing request to RoboHub') and distinguishes from sibling tools like search_robots, get_robot, compare_robots, and 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 Guidelines4/5

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

The description provides clear usage context, mentioning the tool should only be called with the user's explicit consent and real contact details. It implies when to use (when user wants vendor introductions) without explicit exclusions, but the context is sufficient.

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

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

Disambiguation5/5

All five tools have distinct purposes: comparing two robots, fetching a single robot's details, listing categories, submitting vendor intros, and searching. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., compare_robots, get_robot, list_categories) with no mixing of conventions.

Tool Count5/5

Five tools is well-scoped for a robot catalog covering search, retrieval, comparison, category browsing, and vendor intros. No tool feels excessive or missing.

Completeness4/5

Covers search, details, comparison, categories, and vendor intros well. Minor gap: no tool for listing all robots without a query, but search with empty query can likely fill this.

Resources

Need Help?