Skip to main content
Glama

DaedalMap Wildfire 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 declare readOnlyHint=true, and the description adds useful behavioral context beyond that: the exact API contract, the distinction between free and paid packs, and the x402 Base USDC payment requirement. It does not describe the response shape, but safety-related behavior is well covered.

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?

Two sentences deliver the essential purpose, contract, and pack availability with no filler. The primary access mode is front-loaded, and the pack list is compact and directly useful.

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?

With 8 parameters, no required fields in the schema, and no output schema, the description should clarify that a source_id or pack_id must typically be provided. It relies on the external API contract reference and leaves some invocation details implicit. Still, the schema descriptions and pack list cover much of what an agent needs.

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 description coverage is 100%, so the baseline is 3. The description adds the pack list and payment context but does not add parameter-level semantics beyond what the input schema already provides. It only reinforces the source_id/pack_id access model.

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?

The description clearly identifies a specific verb ('query') and resource ('dataset') and explains that it provides direct access via source_id or pack_id. It names the backing API contract. However, it does not explicitly contrast itself with siblings like get_pack or get_catalog, so it stops short of full differentiation.

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: when you have a direct source_id or pack_id and need structured data. It also lists free vs. paid pack availability, which helps selection. But it does not explicitly say when not to use it or point to an alternative sibling tool for catalog listing or pack metadata.

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

All DaedalMap Wildfire 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/5.0
Disambiguation4/5

Tools are mostly distinct: discovery (get_catalog, get_pack), query (query_dataset), and linked-disaster helpers (get_disaster_link_chain, get_disaster_links_for_event, search_disaster_links) are clearly separated. However, get_disaster_link_chain and get_disaster_links_for_event both expand an event id into related events/links, which could cause confusion even though descriptions explain the difference.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: get_catalog, get_pack, get_disaster_link_chain, query_dataset, search_disaster_links. The naming is uniform and predictable.

Tool Count4/5

Seven tools is within the typical well-scoped range. The mix of discovery, query, and helper tools covers the server's facade purpose, though none are strictly wildfire-specific. The count feels reasonable, not excessive or sparse.

Completeness4/5

The server provides discovery (catalog, pack metadata), an arbitrary query interface, and linked-disaster helpers, covering the main access patterns. Minor gaps exist, such as no direct 'list events' tool separate from query, but query_dataset likely handles retrieval. Overall, the surface is coherent for a data-access server.

Resources