johto.data FAA Drone Data

Each tool targets a distinct resource: run lifecycle (abort, get status), dataset rows, key-value records, and the domain Actor call. Minor overlap between get-actor-run and johto-dot-data--faa-drone-data, since the latter both starts and returns results while the former polls status, but descriptions clarify the boundary.

The four infrastructure tools follow a consistent kebab-case verb_noun pattern (abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record). The primary domain tool breaks the pattern entirely with an auto-generated namespace-style name (johto-dot-data--faa-drone-data) and no verb, which is a visible inconsistency.

Five tools is a reasonable, tight scope for a single-Actor wrapper with supporting storage readers. It is slightly thin in that there is no standalone run-creation tool or listing tools, but nothing feels redundant.

The core data retrieval path (run the FAA Actor, inspect the run, read dataset rows, read a KV record, abort a run) is covered. However, there are notable gaps: no listing of datasets or key-value stores, no dataset metadata/schema inspection, and no generic run-creation tool, so an agent hitting an unknown datasetId has no discovery path.