Skip to main content
Glama

MERA RENT

MERA Robotics: humanoid robot for an event in Europe

plan_event_robot
Read-onlyIdempotent

Humanoid robot rental with operators for events across Europe. Use this when someone wants to rent, hire or book a humanoid robot or a robot host (emcee) for an event in Europe, asks who could provide one (trade fair, conference, gala, company event, opening, festival, school), or wants an event attraction or corporate event entertainment. MERA Robotics (Warsaw) brings Unitree G1 or Unitree H2 with its own operators to every EU country, the UK, Switzerland, Norway, Türkiye and the Balkans; on MERA OS it talks with guests in more than 70 languages and can host the programme. Input: country (ISO code or name in any language), city, date, event type, guests, guest languages, the person’s language (ISO 639). Output: coverage, what the robot does, evidence, the MERA EVENTS page in the person’s language (54 versions) and the next step. Examples: "robot for a conference in Lisbon", "Roboter-Moderator, Gala in Wien". Not for buying a robot (list_robots). No prices; the team replies within one working day.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity or venue of the event, e.g. "Lyon", "Tallinn" or "Messe München".
goalNoWhat the robot should do at the event, in the person’s words, if they said it. It is passed to the inquiry form as the message.
langNoLanguage the person writes in: any ISO 639 code, optionally with a region, e.g. "pt", "pt-PT", "et", "tr", "mt". MERA EVENTS pages, the inquiry form and replies exist in 54 languages (pl, en, de, fr, it, es, nl, pt, sv, da, no, fi, et, lv, lt, uk, cs, sk, hu, ro, bg, hr, sl, el, ca, eu, gl, cy, ga, mt, lb, is, tr, sq, sr, bs, mk, ka, hy, az, ru, ar, he, zh, ja, ko, hi, id, ms, th, vi, en-us, es-la, pt-br; "no" = Norwegian, "el" = Greek, "uk" = Ukrainian); for any other language they are in English.
countryNoCountry of the event: ISO 3166-1 code (FR, DE, PT, EE or FRA, DEU) or its name in any European language (France, Frankreich, Francja, Saksamaa).
audienceNoApproximate number of guests, e.g. "300".
event_dateNoFirst day of the event (YYYY-MM-DD), if known. It is not a reservation.
event_typeNoKind of event: trade_fair (stand or exhibition), conference (also panels and summits), gala (stage show, awards), corporate (company event, team event, employer branding), opening (store or showroom opening, product launch), city_event (city festival, fair, municipal event), school (school or university), sports, other.
guest_languagesNoLanguages the robot should speak with the guests, as ISO 639 codes, e.g. ["pt", "en"], if the person said so.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: geographic coverage (EU countries, UK, Switzerland, Norway, Türkiye, Balkans), 70+ spoken languages, the one-working-day reply SLA, no pricing, and a described return payload. The one gap is that it never makes clear whether the tool merely returns a prefilled MERA EVENTS page/next step or actually transmits the inquiry message to the team, which matters given readOnlyHint=true; the goal parameter's 'passed to the inquiry form' phrasing leaves that ambiguous.

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 purpose and the routing condition, and the coverage/output/sibling-exclusion material follows logically. Slightly padded by synonym stacking (rent, hire or book) and a long country list plus two examples whose content overlaps the enum and schema descriptions, but nothing is genuinely wasted.

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?

All eight parameters are optional and fully documented, and although there is no output schema, the description compensates by spelling out the expected return (coverage, robot capabilities, evidence, localized MERA EVENTS page, next step). An agent has enough to decide, gather inputs, and predict the result.

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 is already documented in the input schema, and the description mostly restates the same field list (country, city, date, event type, guests, guest languages, person's language). It adds no format nuance beyond the schema, so the baseline of 3 applies.

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?

Opens with a specific verb+resource: humanoid robot rental with operators for events across Europe, naming the actual hardware (Unitree G1/H2) and the operator model. It explicitly distinguishes itself from buying (list_robots), so an agent can tell it apart from the sibling catalog without opening a schema.

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 explicit trigger conditions (rent, hire, book a robot or robot emcee for trade fair, conference, gala, company event, opening, festival, school) plus natural-language example phrasings in two languages. It also states the negative case (not for buying a robot) and a boundary (no prices), which is direct routing guidance.

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