Skip to main content
Glama

Avioverse EASA library

List the regulations

list_regulations
Read-onlyIdempotent

List the EASA regulations in the library with their official reference, the EAR revision date the text reproduces, and the regulation value to pass to get_rule.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_regulations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 value beyond them by disclosing the shape of the result set: official reference, EAR revision date, and the key needed for chaining into get_rule. It does not mention ordering, cardinality, or pagination, which keeps it at 4 rather than 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 front-loads the action and resource, then enumerates the payload. Every clause (reference, EAR revision date, regulation key for get_rule) earns its place with no filler.

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?

This is a zero-parameter, read-only listing tool with full annotation coverage and no output schema, so the description must carry the return-value information — which it does by naming all three returned fields. Nothing an agent needs to invoke it or use its output correctly is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly avoids inventing filtering options that the empty schema does not support.

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?

Names a specific verb and resource ('List the EASA regulations in the library') and immediately specifies the three fields returned, so an agent knows exactly what it gets. It also ties itself to the get_rule sibling by naming the `regulation` value as the hand-off parameter, distinguishing it from that tool without any schema lookup.

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?

The definition makes the workflow explicit: call this first, then pass the returned `regulation` value to `get_rule`. That is clear context-level guidance. It stops short of a 5 because it gives no exclusions (e.g., when to use `search` or `lookup_term` instead for finding a specific regulation).

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