Skip to main content
Glama

MERA RENT

MERA Robotics: company profile

get_company_profile
Read-onlyIdempotent

Use this when someone asks about MERA Robotics itself: who it is, where it works, its rental fleet, languages, contact or registry data. MERA Robotics (MERA ROBOTICS sp. z o.o., Warsaw, Poland) rents humanoid robots (Unitree G1, Unitree H2) with its own operators and its MERA OS conversation system for events across Europe (every EU country and also the United Kingdom, Switzerland, Norway, Iceland, Türkiye and the Western Balkans, among others) and runs the robot Edward Warchocki. Returns a one-sentence definition, evidence (brands, places, reach, MERA OS), event rental pages in 24 languages, registry data, rental fleet, languages, pricing policy (no published prices), contact and related entities (MERA OS, Edward Warchocki, the merarobots.com shop). 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": "get_company_profile"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value beyond that by disclosing the return payload (one-sentence definition, evidence, registry data, fleet, contact, related entities) and the notable fact that no prices are published.

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 usage trigger is front-loaded, which is good, but the return list is padded and partially redundant – "rental fleet" and "languages" are each mentioned twice, and the long country enumeration plus "among others" adds bulk without helping selection.

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 return contents and does so thoroughly for a one-parameter read tool. Minor gap: it does not clarify how the canonical Polish fact texts interact with the en label parameter.

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% and the single lang enum parameter is fully documented in the schema, so the baseline is 3. The description does not explain the en/pl switch; the mention of "event rental pages in 24 languages" could even be mistaken for the language parameter, which only accepts en and pl.

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 trigger ("when someone asks about MERA Robotics itself") and enumerates exactly what the tool covers: identity, locations, rental fleet, languages, contact, registry data. The agent can tell this apart from an event-planning call 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?

Explicit when-to-use framing plus one explicit alternative: "For a concrete event use plan_event_robot." No exclusion guidance against overlapping siblings such as get_how_we_work, get_media_and_proof, or list_robots, which also touch company/brand facts, so a bit of routing ambiguity remains.

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