Skip to main content
Glama

Avioverse EASA library

Search the library

search
Read-onlyIdempotent

Search EASA rules, EASA definitions, implementation guides, articles and the Metis manual by reference or by words. Returns matching pages with their URLs. A rule reference such as 145.A.30 ranks exact matches first.

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
queryYesWords to look for, or a rule reference such as 145.A.30

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behaviour, so the safety profile is covered. The description adds genuine value by disclosing the ranking rule for exact references such as 145.A.30 and the URL-bearing result format, but it says nothing about result caps, pagination, or what an empty match looks like.

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?

Three short sentences, front-loaded with scope and ending on the ranking nuance. There is minor redundancy between 'by reference or by words' and the schema's parameter description, but nothing wasteful.

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-only search tool with annotations and no output schema, the description covers scope, input kinds, ranking, and return shape. Only result-volume behaviour (limits/pagination) is absent, which is a small 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?

Only one parameter exists and schema coverage is 100%, with the schema already supplying the 'words or a rule reference such as 145.A.30' guidance. The description largely restates that constraint rather than adding new semantics, so the high-coverage baseline of 3 applies.

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 names a specific verb (search) and enumerates the corpora searched (EASA rules, definitions, implementation guides, articles, Metis manual), plus the return shape (matching pages with URLs). This distinguishes it from a tool like get_rule or lookup_term by implication, but no sibling is named explicitly.

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: search by free words or by a rule reference, with exact-reference matches ranked first. There is no explicit statement of when to prefer this over fetch, get_rule, lookup_term, or list_regulations, so the agent must infer the 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