Skip to main content
Glama

MERA RENT

MERA Robotics: robots for rent and sale

list_robots
Read-onlyIdempotent

Use this when someone asks which robots MERA Robotics rents or sells, or about a model’s size, purpose or specifications. For rental with its own operators at events across Europe: Unitree G1 and Unitree H2. For sale: Unitree humanoids, quadrupeds, an industrial robot, a robotic hand, a VR teleoperation kit and inspected used G1 EDU, with type, purpose, key specifications and shop links. No prices: price and availability come from the shop or an inquiry. Where the host supports it, the result is shown as robot cards with an inquiry button.

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_robots"
  }
}

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
typeNoOptional: only robots of this type.
robotNoOptional: return only this robot.
availabilityNo"rent" = robots available for rental with a MERA operator, "sale" = robots for purchase, "all" = both.all

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, idempotent and non-destructive, so the safety bar is met. The description adds genuinely new context: no prices are returned, the rental fleet is operator-accompanied and Europe-scoped, and the result is rendered as robot cards with an inquiry button on supporting hosts.

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 usage trigger is front-loaded and every sentence carries content (rental fleet, sale catalog, no prices, result rendering). It is a single dense paragraph with list-like clauses, slightly heavy but not padded.

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 what comes back: robot type, purpose, key specifications and shop links, presented as cards with an inquiry button. Combined with the no-prices caveat and the rental/sale catalog split, an agent has enough to call it and set expectations.

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 four parameters carry enum values, so the schema fully documents lang, type, robot and availability. The description only indirectly gestures at the rent/sale split and never mentions the language or type filters, so it adds little beyond the schema.

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?

States a specific verb and resource ('which robots MERA Robotics rents or sells') plus the secondary scope of model size, purpose and specifications. An agent can separate this from siblings like list_services or get_company_profile without opening the 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 which robots MERA rents or sells, or about a model's size, purpose or specifications' gives an explicit trigger condition. It also routes price/availability requests away from this tool ('price and availability come from the shop or an inquiry'), though it never names the sibling tools that handle that.

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