Skip to main content
Glama

MERA RENT

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, including robot hire as an event attraction or corporate event entertainment (company party, Christmas party, trade fair stand). 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

NameRequiredDescriptionDefault
cityNoCity or venue town, e.g. "Lisbon".
dateNoEvent day, YYYY-MM-DD.
daysNoNumber of consecutive event days (1-14).
langNoLanguage the person writes in (ISO 639, e.g. "en", "de", "pl"). The MERA RENT app has 24 languages; others get English.
hoursNoRobot time on site per day: up to 2, 4 or 8 hours (the app prices these packages).
robotNoRobot 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.
countryNoCountry of the event: ISO 3166 code ("PT") or name in any language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Despite readOnlyHint=true on a 'book a robot' tool, the description preempts the apparent conflict explicitly: 'It books nothing by itself' — it only produces a deep link and share card, with the person completing the booking in the app. It goes on to disclose the human-side lifecycle (account and form required, date held at least 48 hours, MERA confirms within one working day), which is behavior no annotation conveys.

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 trigger condition, then return payload, then the crucial 'books nothing by itself' caveat, then the alternative tool — a sensible priority order. The event-type enumeration ('company party, Christmas party, trade fair stand') is somewhat padded, but the remaining sentences each carry decision-relevant information.

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?

There is no output schema, so the description carries the return burden and does so: deep link, short share link with preview card, booking steps, and robot list. Combined with the flow caveat (account, form, 48-hour hold, one-working-day confirmation) and the sibling escape hatch, an agent has everything needed to call it and set expectations.

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 every parameter (city, date, days, lang, hours, robot, country) is already documented with formats and examples, making 3 the baseline. The description adds only light framing — that a picker lets the person choose robot, date, hours and city — and does not explain the omitted 'days' parameter or how defaults interact. It mostly restates structured data rather than extending it.

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') plus the concrete scope (MERA operator, event in Europe, a date) and the use cases (event attraction, corporate/company party, Christmas party, trade fair stand). It also implicitly separates catalog mode from booking mode ('start_booking without a robot lists them'), so an agent can tell it apart from list_robots and open_inquiry_form.

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?

Opens with an explicit trigger ('Use this when the person wants to book or reserve a robot... for a date') and gives a clear exclusion plus named alternative: 'For a general inquiry without a chosen date use open_inquiry_form.' It also signals that the person completes the actual booking in the app. It does not distinguish against other date-related siblings such as check_availability, get_rental_quote or plan_event_robot, so routing is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources