Skip to main content
Glama
Sign In
ProgramComputer

NASA MCP Server

by ProgramComputer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

NASA EONET natural events

nasa_eonet
Read-onlyIdempotent

Fetch natural events (wildfires, storms, volcanoes) from NASA's EONET, filtered by category, source, status, and days. Filters are applied exactly as specified.

Instructions

Natural events (wildfires, storms, volcanoes, ice, ...) from the Earth Observatory Natural Event Tracker. Filters are sent exactly as given; no automatic broadening.

Input Schema

NameRequiredDescriptionDefault
daysNoOnly events active within this many prior days.
limitNoMaximum number of events (1-500).
sourceNoEONET source ID(s), comma-separated, e.g. InciWeb,EO.
statusNoEvent status filter.all
categoryNoEONET category ID(s), comma-separated: e.g. wildfires, severeStorms, volcanoes, seaLakeIce.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / category / description
      Previous value: -"Event category (wildfires, volcanoes, etc.)"New value: +"EONET category ID(s), comma-separated: e.g. wildfires, severeStorms, volcanoes, seaLakeIce."
    • addedInput schema / properties / category / pattern
      Added value: +"^[A-Za-z]+(,[A-Za-z]+)*$"
    • addedInput schema / properties / days / default
      Added value: +60
    • changedInput schema / properties / days / description
      Previous value: -"Number of days to look back"New value: +"Only events active within this many prior days."
    • addedInput schema / properties / days / maximum
      Added value: +3650
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of events to return"New value: +"Maximum number of events (1-500)."
    • addedInput schema / properties / limit / maximum
      Added value: +500
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / source / description
      Previous value: -"Data source"New value: +"EONET source ID(s), comma-separated, e.g. InciWeb,EO."
    • addedInput schema / properties / source / pattern
      Added value: +"^[A-Za-z0-9_]+(,[A-Za-z0-9_]+)*$"
    • addedInput schema / properties / status / default
      Added value: +"all"
    • changedInput schema / properties / status / description
      Previous value: -"Event status (open, closed)"New value: +"Event status filter."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "open",
+  "closed",
+  "all"
+]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral note — filters are passed through verbatim with no automatic broadening — but says nothing about result ordering, pagination, or response shape.

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 short sentences with zero filler; the resource and its scope lead, and the filter-behavior caveat follows. Nothing could be trimmed without losing information.

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?

For a read-only query tool with fully documented optional parameters and no output schema, the description covers what the tool is but omits how results are returned and how it relates to overlapping siblings. Adequate, but with clear gaps.

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 all five parameters (days, limit, source, status, category) are already documented with defaults, ranges, and examples. The description adds no parameter-level detail, so the baseline 3 applies.

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 names a specific resource (natural events) and its origin (Earth Observatory Natural Event Tracker) with illustrative examples (wildfires, storms, volcanoes, ice). It is clear what the tool returns, though it does not distinguish itself from the similar sibling nasa_firms, which also covers fire/thermal events.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives among the many NASA siblings, and no indication of when this source is preferable to nasa_firms or nasa_donki. The only guidance given concerns filter strictness, not tool selection.

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

Deploy Server

Other Tools