Skip to main content
Glama

MERA RENT

MERA Robotics: services

list_services
Read-onlyIdempotent

Use this when someone asks what MERA Robotics offers or which service fits their case, including an event attraction or corporate event entertainment to book (company party, Christmas party, team event, trade fair stand) and robot hire with an operator. Services: a humanoid robot with MERA operators at an event anywhere in Europe (also as the event host, conversations in more than 70 languages through MERA OS), campaigns with Edward Warchocki or a branded robot, robot purchase, business deployment, MERA OS for a robot the client owns, media requests. Returns what each covers, when it fits, what the client gets and what is confirmed before commitment, plus booking: the MERA RENT online booking page in the person’s language (https://mera.rent: price under every date, availability calendar, 48 h free hold, 24 languages; same company) and its pages by occasion. No amounts. Where the host supports it, the result is shown as service cards with an inquiry button. For a concrete event use plan_event_robot.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording.en
serviceNoOptional: return only this service.
person_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavior beyond that: it returns what each service covers, when it fits, what the client gets and what is confirmed before commitment, states "No amounts" are returned, and notes results render as service cards with an inquiry button where the host supports it. Minor gap: nothing about result size or how the booking-page links are structured in the payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The when-to-use clause is correctly front-loaded, but the body is one sprawling chain of parentheticals, and the booking-page aside (URL, price under every date, 48 h free hold, 24 languages, "same company") is dense detail that competes with the core service enumeration. It is informative but poorly chunked, making the routing rule harder to extract than it needs to be.

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?

With no output schema, the description carries the burden of describing returns and does so: per-service coverage, fit, deliverables, what is confirmed before commitment, and that no amounts are included. It also covers the booking entry point and the sibling handoff, so only minor edges (result size, exact card fields) are unstated.

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% and all three parameters are documented in the schema, including the full language list for person_lang, so the description can add little. It does implicitly map the enumerated service lines to the `service` enum and ties "in the person's language" to the lang/person_lang distinction, which is a small amount of extra meaning beyond the schema. 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?

Names a specific verb+resource (list MERA Robotics services) and enumerates the covered service lines: humanoid robot with operators, campaigns with Edward Warchocki, robot purchase, business deployment, MERA OS, media requests. It also explicitly distinguishes itself from plan_event_robot, so an agent can pick it without opening 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?

"Use this when someone asks what MERA Robotics offers or which service fits their case" gives a clear positive trigger, and "For a concrete event use plan_event_robot" names the exclusion and the alternative. The occasion list (company party, Christmas party, trade fair stand) further anchors when this applies.

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