Skip to main content
Glama

DaedalMap Tornado Events

by com.daedalmap

Query Dataset

query_dataset
Read-only

Generic structured query for direct source_id or pack_id access using the same contract as POST /api/v1/query/dataset. Free packs: currency, distributed_manufacturing, floods, nri, owid, un_sdg, un_wpp, volcanoes, world_bank_wdi. Paid packs: earthquakes, hurricanes, tornadoes, tsunamis, wildfires, world_factbook, worldpop (x402 Base USDC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOptional sort instructions for row-returning queries.
limitNoMaximum number of rows to return for the requested source or pack.
outputNoOptional output controls such as response format hints.
filtersNoStructured filters including time, region_ids, and compare clauses.
metricsNoMetric ids to return. Use event_count for aggregate counts when supported.
pack_idNoPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
source_idNoConcrete source id such as 'earthquakes_events', 'volcanoes_events', 'hurricanes_events', or 'un_sdg/01'.
request_idNoOptional caller-supplied request id for tracing and idempotency.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description aligns with that by describing a query operation. It adds valuable behavioral context beyond annotations by naming free vs. paid packs and mentioning the x402 Base USDC payment requirement, which an agent would otherwise not know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is stated early, followed by a concise enumeration of packs and pricing. It is information-dense but not bloated; every clause contributes useful selection or cost context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description references an external API contract and lists packs, but with no output schema and many flexible parameters (filters, metrics, output), an agent might need more clarity on response shape or how this relates to get_catalog for discovering pack_ids. It is adequate but leaves some operational context to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds significant value by enumerating actual pack names and differentiating free vs. paid packs. This directly helps agents choose valid pack_id or source_id values beyond the generic schema descriptions.

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?

Description clearly states this is a structured query tool for direct source_id or pack_id access, which distinguishes it from catalog/help/search siblings. It uses a specific verb ('query') and resource, though it could more explicitly contrast with get_catalog and get_pack.

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?

The description implies when to use the tool: querying data from known packs or source ids. It provides a helpful list of available packs, but it does not explicitly state when to prefer this over sibling tools or when not to use it.

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

All DaedalMap Tornado Events toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a distinct purpose: catalog discovery, pack metadata retrieval, tool guidance, dataset querying, and cross-disaster link search. There is no overlap or ambiguity that would cause an agent to misselect a tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_catalog, get_pack, get_tool_help, query_dataset, search_disaster_links), with clear prefixes indicating action type. The naming is uniform and predictable.

Tool Count5/5

Five tools is a well-scoped set for a data discovery and query server. Each tool earns its place, covering discovery, help, generic querying, and cross-event relationship search without unnecessary overlap or bloat.

Completeness5/5

The tool set covers the full lifecycle of data access: discovery (get_catalog, get_pack), guidance (get_tool_help), querying (query_dataset), and cross-disaster linkage (search_disaster_links). There are no obvious gaps that would hinder an agent from accomplishing its tasks.

Resources