Skip to main content
Glama

Avioverse EASA library

Look up a definition

lookup_term
Read-onlyIdempotent

Return how EASA defines a term, quoted verbatim with the regulation and article it comes from, plus the entry from the general aviation glossary when there is 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": {
      "term": "<term>"
    },
    "name": "lookup_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe term to define, for example: error management

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's added value is in the return shape: verbatim quoting with regulation/article attribution, and the conditional glossary entry signaled by 'when there is one'. It stops short of saying what happens for an unmatched term, which is the main remaining behavioral gap.

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?

One front-loaded sentence with zero filler — the primary output (verbatim definition with citation) leads, and the secondary glossary entry follows as a qualified addendum. Nothing is repeated from the title or schema.

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 one-parameter lookup with full annotation coverage, the description is nearly sufficient: it explains the return contents even though no output schema exists. The only shortfall is not addressing the no-match case, which matters for a single-term lookup tool.

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 'term' parameter already has a description with an example, so the schema does the work. The description adds no syntax, format, or casing guidance beyond what the schema provides; 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?

The description states a specific verb-and-resource pair (return EASA's definition of a term) with precise scope: verbatim quote, source regulation and article, plus optional general-aviation glossary entry. This is clearly distinguishable from siblings like search, fetch, or get_rule, which would not carry the verbatim-definition framing.

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 by the purpose — an agent can infer this is the tool for 'what does X mean' questions — but the description never states when to prefer it over search or get_rule, nor what to do when no definition exists. No exclusions or alternatives are named.

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