Genexxis paid agent tools (x402)

airports_status

Disruption check for one airport: active FAA programs (ground stop, ground delay program, arrival/departure delays, closures) with reason and delay minutes, decoded current METAR, 12-hour TAF summary and an overall disruption level none/minor/moderate/severe. Price: $0.008 USDC per call, paid with x402 on Base.

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": {
      "airport": "<airport>"
    },
    "name": "airports_status"
  }
}

Input Schema

Name	Required	Description	Default
`airport`	Yes	US airport IATA/FAA code (JFK) or ICAO code (KJFK)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the priced/paywalled nature up front: $0.008 USDC per call via x402 on Base, which is critical for an agent deciding whether to invoke. It also defines the output taxonomy (none/minor/moderate/severe) and what the delay data includes (reason and minutes), though it omits data freshness, unsupported-airport behavior, and error/cost-failure handling.

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 dense sentence, front-loaded with the purpose and output inventory, with cost appended at the end. Every clause carries information; there is no filler or restatement of the tool name.

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?

No output schema and no annotations, so the description must enumerate returns — it does so thoroughly (FAA program types, METAR, 12-hour TAF, disruption scale) and includes pricing. It stops short of noting data latency, coverage limits (US-only FAA programs), or whether a charge applies to failed lookups.

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 parameter description already states IATA/FAA (JFK) or ICAO (KJFK) formats, more precisely than the description's vague 'one airport'. The description adds no format or validation detail beyond the schema, so 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?

States a specific verb ('disruption check') and resource ('one airport'), then enumerates exactly what is returned: FAA programs, decoded METAR, TAF summary, and an overall disruption level. The composite 'status' scope is distinguishable from the narrower airports_delays and airports_weather siblings even though they aren't named.

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?

'For one airport' implies single-airport lookup rather than bulk scanning, but there is no explicit guidance on when to pick this over airports_delays or airports_weather, both of which clearly overlap. Usage must be inferred from the field list.

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

All Genexxis paid agent tools (x402) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?