Skip to main content
Glama
Sign In

MERA Robotics

by com.merarobotics
OverviewDiscussionsAdmin

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, or asks who could provide one (trade fair, conference, gala, company event, opening, festival, school, sports). MERA Robotics (Warsaw) brings Unitree G1 or Unitree H2 with its own operators to every EU country and also to the United Kingdom, Switzerland and Norway, among others; on MERA OS the robot 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 (any ISO 639 code). Output: coverage, what the robot does, evidence, the MERA EVENTS page in the person’s language (24 languages, otherwise English) and the next step. Examples: "robot for our conference in Lisbon", "Roboter-Moderator für eine 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 24 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; "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. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safe read-only profile (readOnlyHint, idempotentHint, non-destructive), and the description adds genuine context beyond them: geographic coverage (EU plus UK, Switzerland, Norway), 70+ languages, a 24-language page fallback to English, no prices, and a one-working-day reply SLA. A slight gap is that it doesn't clarify that an inquiry is actually transmitted to the team, which matters next to the sibling open_inquiry_form/request_quote.

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?

Purpose is front-loaded in the first sentence, followed by triggers, then scope, then I/O, then exclusions — a logical order. It is dense and runs long as one block, and the input/output recital partially duplicates the schema, but nearly every sentence carries 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?

All 8 parameters are optional and fully documented in-schema, and although there is no output schema the description explicitly previews the return shape (coverage, capabilities, evidence, localized MERA EVENTS page, next step). Nothing an agent needs to invoke this correctly is missing.

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 field already carries a rich description (ISO code acceptance, 24 supported languages, event_type enumeration). The description's "Input: ..." recital restates those fields without adding syntax or constraints, so it lands on the baseline-3 for full schema coverage.

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+scope: "Humanoid robot rental with operators for events across Europe." It then enumerates concrete event categories and the vendor/model (MERA Robotics, Unitree G1/H2), so an agent can immediately distinguish it from the catalogue-style siblings list_robots and list_services.

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?

Explicit triggers ("rent, hire or book", "who could provide one") with parenthetical event types and two multilingual example utterances, plus an explicit exclusion routing buyers to list_robots. The only minor omission is not routing price questions to request_quote, but when-to-use/when-not/alternative are all present.

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

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