Skip to main content
Glama

MERA RENT

Send an inquiry to MERA Robotics

request_quote
Destructive

Sends an inquiry to the company MERA Robotics: the details go to the MERA team, who reply by e-mail to the given address within one working day. This is an outbound message to MERA and cannot be recalled. Use this only after the person has seen exactly what will be sent and agreed to share their name and e-mail with MERA Robotics for this inquiry (contact_consent=true). When the host can show it, prefer open_inquiry_form, where the person sends the form themselves. It does not book a date or confirm a price; MERA does not publish prices. The same inquiry repeated within 24 hours is not sent twice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>",
      "name": "<name>",
      "email": "<email>",
      "message": "<message>",
      "contact_consent": "<contact_consent>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or venue of the event or deployment.
nameYesFull name of the person sending the inquiry, exactly as they gave it.
roleNoJob title, if the person gave one.
emailYesThe person’s own e-mail address; the MERA team replies to it. Never guess it or use a placeholder.
phoneNoPhone number, only if the person chose to give it.
robotNoOptional robot key from list_robots. For rental with an operator only g1 or h2; other keys are for purchase.
budgetNoBudget, only if the person stated one. It is not a MERA price.
companyNoCompany or organisation, if the person gave one.
countryNoCountry of the event or deployment (MERA works across Europe), e.g. "France" or "FR".
messageYesThe goal and what the robot should do, venue conditions and anything else the MERA team should know, in the person’s words.
serviceYesWhat 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.
websiteNoAnti-spam field. Always leave empty.
audienceNoApproximate number of guests or participants.
durationNoHow long the robot should be on site, e.g. "4 h" or "2 days".
languagesNoLanguages the robot should speak with guests, e.g. ["Polish", "English"].
event_dateNoFirst day of the event or the preferred start date (YYYY-MM-DD), if known.
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.
event_end_dateNoLast day of a multi-day event (YYYY-MM-DD).
reply_languageNoThe 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.
contact_consentYesMust be true. Set it only after the person has seen the details that will be sent and agreed to share them with MERA Robotics for this inquiry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses the reply SLA (one working day), the consent precondition, that the message is outbound and cannot be recalled (consistent with destructiveHint=true), and 24-hour duplicate suppression. That duplicate-suppression line sits in mild tension with idempotentHint=false, and error behavior (e.g. a rejected contact_consent) or rate limits are not described, so it falls just short of full transparency.

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: what the tool does, then the irreversibility, then the consent gate, then the preferred alternative, then scope limits. Six sentences is a bit long but each carries distinct information; the "MERA does not publish prices" clause is the one piece that could be trimmed.

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 20-parameter, irreversible outbound action with no output schema, the description covers the essentials: consent requirement, irreversibility, response channel and timing, deduplication, and the sibling alternative. It stops short of describing what a successful call returns or what happens when consent is absent or invalid.

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% across all 20 properties, including enums for service, robot and event_type and the const:true on contact_consent, so the schema already carries the parameter meaning. The description adds only ambient context (no published prices, consent gating) and no extra field-level semantics beyond what is documented, so the baseline 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?

The first sentence names a concrete verb and resource ("sends an inquiry to the company MERA Robotics") and states the delivery path: the details go to the MERA team, who reply by e-mail to the given address. It also carves out what the tool is not ("does not book a date or confirm a price"), which separates it from start_booking and get_rental_quote.

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?

Usage is conditioned explicitly: only after the person has seen exactly what will be sent and agreed to share name and e-mail (contact_consent=true). A named alternative with its selection rule is given — prefer open_inquiry_form when the host can show it, since the person sends the form themselves — plus repeated inquiry within 24 hours is not sent twice.

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