Skip to main content
Glama

MERA RENT

Search MERA Robotics content

search
Read-onlyIdempotent

Use this to find a MERA Robotics document when the other tools do not answer the question: the profile, services (humanoid robot rental with operators for events across Europe first), robots, evidence and knowledge-base articles in Polish, English and German. Returns result ids, titles, URLs and snippets; pass an id to fetch for the full text. Not a general web search.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (1-20).
queryYesSearch words, e.g. "robot rental Lyon" or "MERA OS languages".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world, idempotent and non-destructive, so the safety profile is settled. The description adds genuinely new behavior: the return shape (ids, titles, URLs, snippets) and the handoff to fetch. It stops short of ranking, pagination, or empty-result behavior, which keeps it off a 5.

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 rule is front-loaded in the first clause, and the corpus/return details follow in a single dense sentence. Slight overloading — corpus types, languages, return fields and fetch handoff in one breath — costs a point but nothing is padding.

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?

No output schema exists, yet the description states exactly what comes back and how to escalate to full text, plus corpus scope and languages. With safety covered by annotations, an agent has everything needed to decide to call it and to act on results.

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 both parameters carry descriptions with an example query and the 1-20 limit range, so the schema does the heavy lifting. The description adds only the implicit notion that queries are natural search words; it says nothing about the limit parameter. Baseline 3 applies.

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?

Specific verb+resource: find a MERA Robotics document, with the corpus enumerated (profile, services, robots, evidence, knowledge-base articles) and languages named. It explicitly distinguishes itself from the sibling universe by positioning as fallback and from general web search by negation.

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 selection rule: use only when the other tools do not answer the question, and 'Not a general web search.' It also states the follow-up path — pass a returned id to fetch for full text — so the agent knows the two-step workflow rather than stopping at search.

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