Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver la ficha AIP de un aeródromo

get_aip_aerodromo
Read-only

Retrieve the published AIP AD 2 data sheet for an Ecuadorian aerodrome by ICAO code, including coordinates, runways, frequencies, services, and procedures.

Instructions

Full published AIP AD 2 data sheet for one aerodrome (ICAO code): coordinates, runways, hours, services, frequencies, procedures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
designadorYesICAO code of the aerodrome/helipad, e.g. SEQM (Quito — Mariscal Sucre), SEGU (Guayaquil — José Joaquín de Olmedo), SECU (Cuenca — Mariscal Lamar).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / designador / description
      Added value: +"ICAO code of the aerodrome/helipad, e.g. SEQM (Quito — Mariscal Sucre), SEGU (Guayaquil — José Joaquín de Olmedo), SECU (Cuenca — Mariscal Lamar)."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / designador / title
      Removed value: -"Designador"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / title
      Removed value: -"get_aip_aerodromoArguments"
    • removedOutput schema / title
      Removed value: -"get_aip_aerodromoDictOutput"
  4. First observedv0.8.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds scope value by stating that the full AD 2 sheet is returned, but does not address the format parameter's effect, latency, or any source/freshness caveat for the published AIP data.

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 front-loaded sentence that names the resource first and then enumerates returned sections. No filler, no repetition of the title, no restatement of schema fields.

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 simple read-only single-record lookup with fully documented parameters and annotations covering safety, the description is close to sufficient. It stops short only on routing (which list tool to use first) and on the fact that the response shape is governed by the format parameter, but no output schema exists that would carry that detail.

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 both parameters are well documented in the schema itself (ICAO code with real examples, format enum with default). The description adds no meaning beyond that, so the baseline 3 is appropriate.

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?

States a specific resource, 'full published AIP AD 2 data sheet for one aerodrome', keyed by ICAO code, and enumerates the sections returned (coordinates, runways, hours, services, frequencies, procedures). The singular 'one aerodrome' distinguishes it implicitly from a list operation, but it never names the sibling list_aip_aerodromos, so an agent must infer the distinction.

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 only implied: 'one aerodrome (ICAO code)' signals a single-record detail lookup versus a browsing/list tool, but there is no explicit when-to-use statement, no prerequisite (e.g. resolving the ICAO code first), and no named alternative such as list_aip_aerodromos.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools