Skip to main content
Glama

Donki Cme

donki_cme
Read-onlyIdempotent

"Was there a coronal mass ejection this week?" / "is a CME heading for Earth?", coronal mass ejections catalogued by NASA DONKI, the space-weather event database run by NASA's Community Coordinated Modeling Center. AUTHORITATIVE for CME occurrence and geometry: returns each eruption's start time, the instruments that saw it, the analysts' note describing the source region, and for analysed events the modelled speed in km/s, the direction (latitude/longitude on the solar disk), half-angle width and whether the analysis is the most accurate available. A CME is the thing that causes an aurora or a satellite drag event two or three days later, so speed plus direction is what says whether it will reach Earth.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 3,
      "end_date": "2026-09-17",
      "start_date": "2026-09-01"
    },
    "name": "donki_cme"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events to return (default 50, max 200).
_apiKeyNoNASA API key (optional, defaults to DEMO_KEY)
end_dateNoEnd date YYYY-MM-DD (optional; defaults to today).
start_dateNoStart date YYYY-MM-DD (optional; DONKI defaults to ~30 days ago).
min_speed_km_sNoOnly return CMEs whose best analysis measured at least this speed in km/s. ~500 is fast, ~1000+ is a major event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description adds useful context about the authoritative source and the specific eruption fields returned, including modelled speed, direction, half-angle width, and analysis accuracy. It does not discuss rate limits, authentication behavior beyond the schema, or pagination, keeping it below a 5.

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 description is front-loaded with concrete use-case questions and then explains the event type and returned fields. It is generally efficient, though the final sentence about aurora and satellite-drag consequences is explanatory rather than strictly necessary for invocation.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing returns and does so thoroughly: start time, instruments, analyst notes, modelled speed, direction, width, and analysis quality. For a zero-required-parameter, fully schema-documented listing tool, this is sufficient context to select and invoke it correctly.

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 parameter meanings are fully supplied by the schema; the description adds no filter-specific guidance beyond noting that speed and direction indicate Earth arrival. A baseline 3 is appropriate because the description does not meaningfully extend parameter semantics.

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?

The description names the exact resource (coronal mass ejections), the authoritative source (NASA DONKI/CCMC), and provides concrete user-question examples that make the tool's scope unmistakable. It also distinguishes CMEs from related space-weather events by describing eruption geometry and Earth-reach implications.

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?

The opening example questions (“Was there a CME this week?” / “is a CME heading for Earth?”) give clear usage contexts, and the domain explanation indicates when speed/direction matter. It does not explicitly name sibling tools such as donki_geomagnetic_storms or state when not to use this tool, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.