Skip to main content
Glama

DaedalMap Disaster and Geospatial Data

by com.daedalmap

Search Disaster Links

search_disaster_links
Read-only

Free linked-disaster discovery helper. Searches published cross-disaster link families by event-type direction, optional via-event type, and optional year window. Use this when you want to discover whether a relationship family exists before you have an exact event id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of matching chains to return. Default 10.
year_endNoOptional inclusive ending year filter.
request_idNoOptional caller-supplied request id for tracing.
year_startNoOptional inclusive starting year filter.
end_event_typeNoOptional ending event type such as tsunami, flood, tornado, or earthquake.
via_event_typeNoOptional intermediate event type for bounded chain discovery.
start_event_typeNoOptional starting event type such as earthquake, hurricane, volcano, wildfire, flood, tornado, or tsunami.

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true. The description adds 'Free linked-disaster discovery helper' and mentions searching published families, but does not detail search algorithm or output format. With annotations, this is adequate; no additional behavioral disclosure needed.

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 front-loading purpose and usage. No redundant or extra words. Every sentence adds value.

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?

Despite no output schema, the description is sufficient for a discovery tool with 7 optional parameters. It covers purpose and usage context. Slightly incomplete regarding output nature, but acceptable given the tool's simplicity and annotations.

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 parameters are fully documented in the schema. The description mentions 'event-type direction, optional via-event type, and optional year window,' which maps to start_event_type, end_event_type, via_event_type, year_start, year_end, but adds no new meaning beyond the schema. Baseline score of 3 is appropriate.

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?

Description clearly states the tool's function: 'Searches published cross-disaster link families' with specific parameters (event-type direction, optional via-event type, year window). It distinguishes from siblings like 'get_disaster_link_chain' (which requires an exact event ID) by focusing on discovery before having an exact ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance: 'Use this when you want to discover whether a relationship family exists before you have an exact event id.' This indicates the usage context and implies alternatives (e.g., get_disaster_link_chain for known IDs), but lacks explicit exclusions.

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

All DaedalMap Disaster and Geospatial Data 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

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct scopes with detailed 'Use this' guidance, but a few pairs like get_disaster_link_chain and get_disaster_links_for_event, or query_dataset versus the specialized get_* event tools, could cause momentary confusion. Overall, descriptions mitigate overlap well.

Naming Consistency4/5

The majority follow a consistent verb_noun pattern (check_, compare_, convert_, create_, estimate_, get_, list_, resolve_). Minor exceptions like loc_id_info and query_dataset are acceptable but break the pattern slightly.

Tool Count3/5

28 tools exceed the preferred range, but the broad domain spanning disasters, geospatial geometry, reference conversion, and export jobs justifies many of them. Still, the count feels heavy and might overwhelm agents.

Completeness5/5

The tool surface is remarkably comprehensive: discovery (catalog, pack, geometry catalog), resolution (point, reference, scope), geometry (check, get, compare), conversion (quote, create, status), and disaster events for multiple types. No critical dead ends for the stated domain.

Resources