MERA Robotics

MERA RENT: price for a robot on a date

get_rental_quote

Read-onlyIdempotent

Use this when someone asks how much it costs to rent a MERA RENT robot on a given date, for a number of hours, in a city. MERA never gives amounts outside its app, so this returns no amount: it returns the MERA RENT link that shows the exact price for that robot, date, hours (up to 2, 4 or 8 h per day) and country, what the price includes (operator, travel in Europe, conversations in more than 70 languages), the payment rule (100% before the event), the calendar status of the date and the arguments for start_booking. Never state or estimate a price yourself.

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": {
      "robot": "<robot>",
      "date": "<date>"
    },
    "name": "get_rental_quote"
  }
}

Input Schema

Name	Required	Description
`city`	No	City or venue town, e.g. "Lisbon".
`date`	Yes	Event day, YYYY-MM-DD.
`days`	No	Number of consecutive event days (1-14).
`lang`	No	Language the person writes in (ISO 639, e.g. "en", "de", "pl"). The MERA RENT app has 24 languages; others get English.
`hours`	No	Robot time on site per day: up to 2, 4 or 8 hours (the app prices these packages).
`robot`	Yes	Robot id from MERA RENT, e.g. "g1" (Unitree G1), "h2" (Unitree H2), "go2" (Unitree Go2), "edward" (Edward Warchocki) or a catalog model such as "unitree-h1"; start_booking without a robot lists them.
`country`	No	Country of the event: ISO 3166 code ("PT") or name in any language.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the basic safety profile is covered. The description adds useful behavioral detail: it never returns an amount, it returns a MERA RENT link, and it includes the payment rule and calendar status. That is meaningful extra context, but the return shape is only summarized rather than specified, so a 3 rather than a 4.

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?

The description is a single dense paragraph that is front-loaded with the trigger condition and then the return contract. Every sentence carries information, though the mid-paragraph list of inclusions (operator, travel, languages, payment rule) is slightly packed and could be trimmed without losing meaning.

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?

There is no output schema, so the description must explain what comes back, and it does: a link, price inclusions, payment rule, calendar status, and start_booking arguments. That is enough to call the tool correctly, though it stops short of describing the response structure or error cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning: 'hours (up to 2, 4 or 8 h per day)' explains how the app prices packages, and 'the exact price for that robot, date, hours and country' shows which parameters drive the result. The lang and days parameters are not addressed in the text, but the schema covers them.

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 description names a specific verb and resource (quote a rental price for a MERA RENT robot on a date) and bounds the scope with city, hours, and country. It is clearly distinguishable from siblings like request_quote and start_booking, and the title plus opening clause make the intent unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger ('Use this when someone asks how much it costs to rent... on a given date'), which is stronger than implied usage, and it returns arguments for start_booking, so the agent can follow the correct tool sequence. It does not explicitly name when to prefer request_quote or check_availability instead, so a 4 rather than a 5.

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

All MERA Robotics tools Inspect

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

Need Help?