Skip to main content
Glama

Avioverse EASA library

Get an EASA rule by reference

get_rule
Read-onlyIdempotent

Return an EASA rule by its reference (for example 145.A.30(e), CAMO.A.305, ORO.GEN.200, FCL.010) with its text, AMC and GM, the regulation, the EAR revision date and the page URL. A rule published point by point lists its points to request next. If several regulations use the reference (such as Article 2), the matches are listed: pass regulation to choose one.

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": {
      "reference": "<reference>"
    },
    "name": "get_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesRule reference, for example 145.A.30(e)
regulationNoRegulation slug from list_regulations, only needed when a reference is shared

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/closed-world safety, but the description adds genuinely useful behavior: a point-by-point rule returns its points "to request next" (a partial-response contract), and an ambiguous reference returns a match list instead of guessing. What's missing is any statement about a not-found reference, though that is a minor gap against otherwise rich disclosure.

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?

Three sentences, front-loaded with the return payload, then the two edge-case behaviors an agent actually needs. No filler, no restatement of the tool name.

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, so the description carries the return-value burden and does it fully: content set, provenance (regulation, EAR revision date), and page URL. Combined with the ambiguity and point-by-point handling, an agent has everything needed to call it and interpret the result.

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 description coverage is 100%, and the schema already labels `regulation` as a "Regulation slug from list_regulations, only needed when a reference is shared." The description's restatement of that conditional adds little new meaning beyond the structured field, so the baseline of 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?

States a specific verb+resource ("Return an EASA rule by its reference") and enumerates exactly what comes back: text, AMC and GM, regulation, EAR revision date, page URL. The by-reference nature makes it clearly distinct from siblings like search and lookup_term, which cannot be inferred to do the same.

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 concrete request examples (145.A.30(e), CAMO.A.305, ORO.GEN.200, FCL.010) and explicitly says when to supply `regulation`: only when several regulations share the reference, as with Article 2. It does not name a sibling for the discovery case (e.g. use search when you don't know the reference), so guidance is strong but not exhaustive.

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