Skip to main content
Glama

MERA RENT

MERA Robotics: inquiry form

open_inquiry_form
Read-onlyIdempotent

Use this when the person wants to ask MERA Robotics about a date for a robot at an event anywhere in Europe, or about a rental, purchase or deployment. Shows an inquiry form in the chat in the person’s language (24 languages, otherwise English), prefilled with details they already gave (service, event type, robot, date, city, country, guests, languages, goal, name, e-mail). It sends nothing by itself: the person checks the details, ticks consent and clicks "Send inquiry" in the form. If the host cannot show the form, collect the details in the chat and use request_quote after the person agrees.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional prefill. City or venue of the event or deployment.
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.
nameNoOptional prefill. Full name of the person sending the inquiry, exactly as they gave it.
emailNoOptional prefill. The person’s own e-mail address; the MERA team replies to it. Never guess it or use a placeholder.
robotNoOptional prefill. Optional robot key from list_robots. For rental with an operator only g1 or h2; other keys are for purchase.
companyNoOptional prefill. Company or organisation, if the person gave one.
countryNoOptional prefill. Country of the event or deployment (MERA works across Europe), e.g. "France" or "FR".
messageNoOptional prefill. The goal and what the robot should do, venue conditions and anything else the MERA team should know, in the person’s words.
serviceNoOptional prefill. What the inquiry is about: events = a humanoid robot with a MERA operator at an event; purchase = buying a Unitree robot; integration = a robot deployed in a business (showroom, reception, booth); mera-os = MERA OS conversation software for a robot the person already owns; campaign = Edward Warchocki or a branded robot in a marketing campaign; media = interview or editorial request.
audienceNoOptional prefill. Approximate number of guests or participants.
durationNoOptional prefill. How long the robot should be on site, e.g. "4 h" or "2 days".
languagesNoOptional prefill. Languages the robot should speak with guests, e.g. ["Polish", "English"].
event_dateNoOptional prefill. First day of the event or the preferred start date (YYYY-MM-DD), if known.
event_typeNoOptional prefill. Kind 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.
reply_languageNoOptional prefill. The person’s language, usually the one they write in: any ISO 639 code, optionally with a region ("pt", "pt-PT", "tr"). MERA replies and sends the event page in it when it is one of the 24 MERA EVENTS 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), otherwise in English; the language is recorded either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare read-only/safe; the description adds what actually matters: the form is prefilled, it sends nothing by itself, the person must tick consent and click Send, and language fallback to English. It also discloses the failure mode and fallback tool, which 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 trigger, then behavior, then fallback — a logical order with little waste. The parenthetical list of prefill fields is somewhat redundant against the schema and the 24-vs-54 language detail is unnecessary noise.

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?

For a 15-parameter, all-optional prefill tool with no output schema, the description covers trigger, behavior, consent step, language handling, and host failure fallback. Only the post-submission outcome (what the person sees after clicking Send) is left implicit, which is a minor gap given the tool itself sends nothing.

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 every parameter already has a rich description with enums, so the schema carries the parameter burden. The description only groups the prefill fields generically and even states 24 languages for the form where the lang parameter documents 54, adding no useful semantics beyond the schema.

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 concrete action (show an inquiry form in the chat) plus the resource and the business scope (event date, rental, purchase, deployment anywhere in Europe). An agent can distinguish it from request_quote without consulting any 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?

Opens with an explicit trigger ('Use this when the person wants to ask...') and names the alternative path with its condition: if the host cannot show the form, collect details and use request_quote after agreement. Both when-to-use and when-not are covered.

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