Retrieves recent arrivals from OpenSky when available, with a keyless nearby-aircraft fallback from Airplanes.live. The fallback is explicitly labeled as live traffic, not confirmed arrivals.
| Name | Required | Description | Default |
|---|---|---|---|
| airport_icao | Yes | 4-character ICAO airport code (e.g. EDDF) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosing behavior. It reveals the fallback mechanism and labeling, but lacks details on authentication, rate limits, error handling, or what happens when both sources are unavailable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, concise, and front-loaded with the primary action. Every sentence adds value without unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description covers the data source and fallback but omits the return format or structure of the response. It is adequate but leaves some gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema coverage is 100% and the description does not add meaning beyond what is already in the schema (e.g., airport_icao is described as a 4-character ICAO code with an example). Baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves recent arrivals from two data sources with a fallback, distinguishing it from sibling tools like getFaaDelays or trackAirspace. However, the name 'getAirportBoard' could imply both arrivals and departures; description specifies arrivals, which is good but not perfect.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions the tool is used when OpenSky data is available with a fallback, but does not provide explicit guidance on when to prefer this tool over alternatives or when not to use it. No usage context or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping functionality, e.g., auditNetworkHost combines DNS, SSL, and header checks that have dedicated tools (auditDnsSecurity, checkSslExpiry, auditSecurityHeaders). Multiple weather and blockchain tools also overlap in scope, making it difficult for an agent to choose the right tool.
Most tools follow a consistent verb_noun pattern (e.g., getAirQuality, checkDnsPropagation), but a few deviate (agentPreflight, capabilitiesDiff) and some use compound names (depositCoordinationBounty). Overall, the pattern is clear but not perfectly uniform.
With 56 tools, the server is far too large for a coherent MCP surface. The number suggests a collection of many unrelated APIs rather than a focused tool set. A typical well-scoped server has 3-15 tools.
While the tool set covers many domains, each domain has shallow coverage. For example, blockchain tools miss basic transaction sending and contract deployment; weather tools lack forecasts. The 'requestMissingData' endpoint acknowledges gaps, but the current surface is severely incomplete for a general-purpose API.