Queries the FAA public API for active delays, ground stops, and weather statuses for a US airport. Matches: air traffic control delays, US airport ground stops, flight weather delays, FAA flight restrictions, airport layout status.
| Name | Required | Description | Default |
|---|---|---|---|
| airport_code | Yes | 3-character IATA airport code (e.g. SFO) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits. It does not mention authentication needs, rate limits, or whether the operation is safe. It only describes the data types returned, not the behavior.
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: the first states the action and scope, the second lists related terms. No redundant words, front-loaded with key function.
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 tool with one parameter and no output schema, the description covers the essential function and parameter. However, lack of usage guidelines and behavioral info prevents a perfect score.
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?
Schema coverage is 100% and already provides pattern and examples. The description adds that it's for a US airport, which is useful but minimal. It does not compensate for any gaps since there are none.
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 verb 'Queries' and the resource 'FAA public API for active delays, ground stops, and weather statuses for a US airport'. It also lists matches that differentiate it from siblings like getAirportBoard or trackAirspace.
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?
No explicit guidance on when to use this vs alternatives. The description does not mention exclusions or prerequisites. Siblings include other aviation tools, but no differentiation is 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.