CEV-OS Data API

NASA natural events and fire counts (TRIPWIRE)

get_natural_events

Read-onlyIdempotent

Use this when you need NASA EONET open natural events (Smithsonian/SIVolcano sources dropped) plus NASA FIRMS fire-detection counts per country per day. Free. License: cleared_with_attribution. Attribution required: NASA Earth Observatory Natural Event Tracker (https://eonet.gsfc.nasa.gov/). Cite NASA. NASA FIRMS (https://earthdata.nasa.gov/firms), part of NASA LANCE / ESDIS. Cite NASA. Events sourced from the Smithsonian Institution / SIVolcano are omitted (non-commercial terms).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_natural_events"
  }
}

Input Schema

Name	Required	Description	Default
`country`	No	ISO 3166-1 alpha-2 filter.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, so the description isn't carrying the safety load. It does add genuinely useful context: a data-source exclusion (Smithsonian/SIVolcano events dropped) and attribution/licensing obligations, but says nothing about return shape, granularity of fire counts, or coverage limits.

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

Conciseness3/5

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

Purpose is front-loaded, which is good, but roughly half the text is repeated licensing/attribution boilerplate with two full URLs and a duplicated "Cite NASA" instruction, diluting the operational content.

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?

For a zero-required-parameter, no-output-schema read tool with rich annotations, this covers source, exclusions, and cost/licensing. Only the shape of returned events and fire counts is left implicit, which is a minor gap.

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% and the single optional country parameter is fully documented with its regex pattern in the schema. The phrase "per country per day" hints at the filter and output granularity but adds no syntax or behavioral detail beyond the schema.

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?

States a concrete verb+resource: NASA EONET open natural events plus NASA FIRMS fire-detection counts per country per day. Clear enough to distinguish from sibling hazard/weather tools by data source, though it doesn't name the nearest alternatives explicitly.

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?

"Use this when you need ..." gives a usage cue, but there is no when-not guidance and no routing against sibling tools like get_hazard_alerts, get_severe_weather, or get_outbreaks, which overlap conceptually.

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

All CEV-OS Data API 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?