MERA Robotics

MERA RENT: is the robot free on this date?

check_availability

Read-onlyIdempotent

Use this when someone asks whether a MERA RENT robot (Unitree G1, Unitree H2, Unitree Go2, Edward Warchocki or a catalog model) is free on a day or in a range of days. Returns each day as free, held (temporarily held by another request, may free up), busy, on_request (model without a public calendar), too_soon (under 2 days ahead) or beyond_calendar, plus the MERA RENT link for that robot and date. Reads only the public calendar: no client names or bookings. Free is not a reservation: MERA confirms the date after the booking request. Ranges up to 62 days. Not for prices (get_rental_quote) and it does not book (start_booking).

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

Input Schema

Name	Required	Description
`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.
`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.
`date_to`	No	Optional last day of a range to check (up to 62 days from date).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: it reads only the public calendar with no client names, 'free' is not a reservation and requires later confirmation, and ranges are capped at 62 days. However, the status vocabulary (free/held/busy/on_request/too_soon/beyond_calendar) is stated without explaining what an agent should do differently for 'held' versus 'on_request' beyond the parentheticals.

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-loads the trigger, then the return shape, then the caveats and exclusions in a logical order with no filler sentences. It is dense, though, and the long status enumeration in a single clause makes it harder to scan than a short bulleted list would be.

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 no output schema, the description still explains the return payload (per-day status plus a MERA RENT link) and the meaning of each status. It also covers the key business caveat that availability is not a confirmed reservation, which is the main way an agent could misuse the result.

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%, so every parameter is already documented, including the 1-14 day window and the date_to 62-day limit. The description restates the 62-day range bound and names the robot ids, which largely duplicates the schema rather than adding syntax or interaction rules. Baseline 3 applies when the schema does the heavy lifting.

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?

Opens with a specific verb+resource ('whether a MERA RENT robot ... is free on a day or in a range of days') and enumerates the concrete robot families covered. An agent can immediately distinguish this from list_robots or 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?

Gives an explicit trigger ('Use this when someone asks whether ... is free'), then names the two nearest alternatives and their domains: prices go to get_rental_quote and booking goes to start_booking. Both positive and negative routing guidance are present.

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?