Skip to main content
Glama

MERA RENT

Fetch a MERA Robotics document

fetch
Read-onlyIdempotent

Use this after search to read one MERA Robotics document in full: returns the Markdown text of an id such as "en:profile", "pl:service:events", "en:robot:g1" or "blog:", with its URL and language.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDocument id returned by the search tool.

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the valuable non-annotation detail that the response is the full document as Markdown plus its URL and language. It does not say what happens with an unknown or malformed id, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that leads with the usage trigger, then the return contract, then id examples. No filler, and the most decision-relevant clause comes first.

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?

One parameter, no output schema, and the description compensates by describing the return shape (Markdown, URL, language). Combined with annotations covering safety, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already says the id comes from search, so baseline would be 3. The description goes beyond that by showing concrete id shapes ("en:profile", "pl:service:events", "en:robot:g1", "blog:<slug>"), which teaches the agent the language-prefix and type-segment convention the schema never states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("read one MERA Robotics document in full") plus the return payload (Markdown text, URL, language), so the agent knows exactly what it gets. It distinguishes itself from `search` via "after search", but does not clarify how it relates to the structured getters (get_company_profile, list_robots) that also surface MERA content.

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 after search" gives an explicit precondition and positions it as the follow-up step to the search tool. No exclusion is stated for the case where a structured getter would be preferable, which is the only remaining gap.

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