Skip to main content
Glama

MERA RENT

MERA Robotics: how cooperation works

get_how_we_work
Read-onlyIdempotent

Use this when someone asks how renting or buying from MERA Robotics works: steps from inquiry to the robot on site anywhere in Europe, what the robot does at an event (including the role of event host), purchase and deployment, languages (more than 70 for robot conversations), pricing policy, what to include in an inquiry and what an inquiry does not do (it does not book a date or confirm a price).

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

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

A3.9/5.0
Behavior3/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 useful scope context — notably that inquiries neither book dates nor confirm prices, which prevents misuse — but says nothing about the shape or freshness of the returned content. With annotations carrying the behavioral load, a 3 is appropriate.

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?

One front-loaded sentence with a colon-delimited scope list — efficient and topic-first. The nested parentheticals make it slightly dense for a single run-on sentence, but no clause is filler.

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 one optional parameter, no output schema, and full annotation coverage, the description supplies what an agent needs: the topics the answer covers and the limits of an inquiry. Only the nature of the returned text (static policy copy vs. dynamic) is left unstated, a minor gap.

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 parameter already documents its enum, default, and the Polish-canonical fact wording. The description's mention of 'more than 70 languages' refers to robot conversation languages, not the lang parameter, so it adds no semantic detail and could momentarily blur the distinction.

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 resource — how renting/buying from MERA Robotics works — and enumerates its scope (inquiry-to-deployment steps, on-site role, purchase, languages, pricing policy, inquiry limits). This clearly separates it from get_company_profile, list_services, and request_quote without needing the schemas.

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 renting or buying... works" gives a clear triggering condition, and the closing note that an inquiry does not book a date or confirm a price sets a boundary. It stops short of naming alternatives (e.g., request_quote for an actual price), so no explicit sibling routing.

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