MERA Robotics

MERA RENT: book a robot

start_booking

Read-onlyIdempotent

Use this when the person wants to book or reserve a robot from MERA RENT (with a MERA operator, for an event in Europe) for a date. Returns a deep link that opens the MERA RENT app with the robot and date chosen, a short share link with a preview card, the booking steps and the list of robots. Where the host shows apps, a picker lets the person choose the robot, date, hours and city, check the date and open MERA RENT. It books nothing by itself: the person completes the booking in the app (account, form; the date is held for at least 48 hours and MERA confirms within one working day). For a general inquiry without a chosen date use open_inquiry_form.

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

Input Schema

Name	Required	Description
`city`	No	City or venue town, e.g. "Lisbon".
`date`	No	Event day, YYYY-MM-DD.
`days`	No	Number of consecutive event days (1-14).
`lang`	No	Language the person writes in (ISO 639, e.g. "en", "de", "pl"). The MERA RENT app has 24 languages; others get English.
`hours`	No	Robot time on site per day: up to 2, 4 or 8 hours (the app prices these packages).
`robot`	No	Robot id from MERA RENT, e.g. "g1" (Unitree G1), "h2" (Unitree H2), "go2" (Unitree Go2), "edward" (Edward Warchocki) or a catalog model such as "unitree-h1"; start_booking without a robot lists them.
`country`	No	Country of the event: ISO 3166 code ("PT") or name in any language.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial behavior beyond the annotations: it returns a deep link, share link, booking steps and robot list, and crucially clarifies "It books nothing by itself" with the 48-hour hold and one-working-day confirmation, which reconciles the book-sounding name with readOnlyHint=true. Missing only minor details such as the format of the returned links.

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 use condition and the routing alternative; every sentence carries information about returns, side effects, or exclusions. It is dense and slightly long, but no sentence is filler.

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?

With no output schema, the description correctly explains the return payload and the human follow-up flow, covering what an agent needs for a 7-parameter, all-optional, booking-adjacent tool.

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 coverage is 100% and each parameter already carries a rich description, so the baseline is 3. The description restates the picker flow (robot, date, hours, city) and the no-robot listing behavior, but adds little meaning the schema does not already contain.

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?

States a specific verb and resource ("book or reserve a robot from MERA RENT") with scope qualifiers (with a MERA operator, event in Europe, for a date), so it is immediately distinguishable from check_availability, get_rental_quote, or list_robots.

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?

Gives the exact triggering condition ("when the person wants to book... for a date") and names the alternative with its own condition: "For a general inquiry without a chosen date use open_inquiry_form." It also notes that calling it without a robot just lists robots, which prevents misuse.

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

All MERA Robotics 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?