Skip to main content
Glama

MERA RENT

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. Returns the net price (excluding VAT) from the MERA RENT price list for that robot, date, hours (up to 2, 4 or 8 h per day), number of days and country, the MERA RENT link that shows the same price, 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. Edward Warchocki and models on request have no list price (individual quote). Quote only the returned amount; never 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

NameRequiredDescriptionDefault
cityNoCity or venue town, e.g. "Lisbon".
dateYesEvent day, YYYY-MM-DD.
daysNoNumber of consecutive event days (1-14).
langNoLanguage the person writes in (ISO 639, e.g. "en", "de", "pl"). The MERA RENT app has 24 languages; others get English.
hoursNoRobot time on site per day: up to 2, 4 or 8 hours (the app prices these packages).
robotYesRobot 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.
countryNoCountry of the event: ISO 3166 code ("PT") or name in any language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantial context beyond them: the price excludes VAT, comes from the official price list, and the response includes the matching MERA RENT link, inclusions (operator, European travel, 70+ languages), payment rule (100% before the event), calendar status, and the arguments for start_booking. It also discloses a real failure mode — models with no list price — which the annotations cannot express.

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 trigger condition is front-loaded in the first clause and the pricing rule at the end, so the key points land where an agent looks. It is dense but nearly every clause carries new information; minor waste exists in restating the 2/4/8 hour packages already encoded in the enum.

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?

With seven parameters and no output schema, the description must explain the return value, and it does so thoroughly: net price excluding VAT, proof link, inclusions, payment rule, calendar status, and start_booking arguments. Nothing required to interpret or invoke the tool 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 description coverage is 100%, so every parameter is already documented, including the hours enum and robot id examples. The description adds only the framing that robot, date, hours, days and country together determine the price, and repeats the 2/4/8 h enum already in the schema. That is a modest semantic addition over structured data, consistent with the baseline 3.

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 states a specific verb and resource: it returns the net rental price for a MERA RENT robot on a given date, in a city, for a number of hours. It also carves out a clear boundary — Edward Warchocki and models on request have no list price and go to an individual quote — which separates it from start_booking and request_quote without needing either schema.

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?

'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' gives an explicit trigger condition. It also implies the exclusion (models without a list price need an individual quote) and adds the guardrail 'Quote only the returned amount; never estimate a price yourself.' The only gap is that the alternative tool for non-list-price cases is described rather than named.

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