Skip to main content
Glama

Avioverse EASA library

Read a page

fetch
Read-onlyIdempotent

Return the full text of one library page as Markdown. id is the id (site path) or url of a result from 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id or url of a search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the agent knows the safety profile without the description. The description contributes the return format (full text as Markdown) and scope (one page), which are useful, but says nothing about size limits, truncation, or failure behavior for a read that may return very large content.

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?

Two short sentences, zero filler, with the action and output format front-loaded and the parameter clarification following. Every sentence earns its place.

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?

For a single-parameter read tool with no output schema and a full annotation set, the description covers what it does, what it returns, and where the input comes from. Missing only edge-case behavior such as oversized pages or invalid ids, which is a minor gap at this complexity.

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 describes the parameter as 'The id or url of a search result.' The description adds real meaning by clarifying that the id form is a 'site path' and that a full url is accepted, which removes ambiguity about what string to pass.

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?

The description states a specific verb and resource with output format: 'Return the full text of one library page as Markdown.' It implicitly distinguishes itself from `search` by describing the id as coming 'from a result from `search`', so an agent can tell that search finds pages and fetch reads them, though the contrast is never made explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the prerequisite that `id` be taken from a `search` result, which conveys the search-then-fetch workflow. There is no explicit when-to-use/when-not statement and no guidance on what to do if the page is missing or the id is a stale result.

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