Skip to main content
Glama

MERA RENT

MERA Robotics: media coverage and evidence

get_media_and_proof
Read-onlyIdempotent

Use this when someone asks for proof, references, press coverage or past projects of MERA Robotics before choosing a provider. Returns independent coverage (Reuters, CNN, BBC News, CBS News, Channel 4 News, Fox Business, ThePrint, Universe Magazine) with the subject of each item (mostly Edward Warchocki; not an endorsement of services), Wikipedia and Wikidata entries for Edward Warchocki, documented projects and campaign results labelled as first-party data. Where the host supports it, the result is shown as source cards.

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

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.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered. The description adds substantial context beyond that: it discloses the provenance mix (independent outlets vs. first-party data), flags that sources are 'not an endorsement of services', and notes the rendering depends on host support ('source cards'). Return format beyond that is not described.

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 trigger is front-loaded in the first clause and every subsequent clause adds a distinct fact about the return set. It is a long single sentence with a bulky eight-outlet parenthetical and nested parentheticals that make it denser than necessary, but nothing is wasted.

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 returns, and it does so by listing content categories, provenance labelling, and card rendering. Minor gap: it doesn't indicate ordering, volume, or whether any of the listed sources may be absent.

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 has a detailed enum description with default and usage rule, so the description need not and does not touch it. 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-plus-resource: returns media coverage and evidence about MERA Robotics, enumerating the exact content classes (press items, Wikipedia/Wikidata, documented projects, campaign results). It is clearly separable from get_company_profile or get_how_we_work by naming 'proof, references, press coverage or past projects' as its domain.

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?

Gives an explicit trigger: 'when someone asks for proof, references, press coverage or past projects ... before choosing a provider'. That is a clear use context. It does not name a sibling (e.g. get_company_profile) as the alternative or state when not to call it, so it stops short of a 5.

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