Skip to main content
Glama

Kp Index

kp_index
Read-onlyIdempotent

NOAA planetary K-index, global geomagnetic activity 0-9, the standard aurora/storm indicator (Kp≥5 is a geomagnetic storm). Windows: now (single freshest estimated value) | 1-day (3-hourly observed, feed carries about a week) | 7-day (observed plus 3-day forecast; each row flags which) | 1-minute (1-minute estimated, last ~6 hours). SWPC retired its 30-day archive, so no month-long Kp history is available from this source.

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": {
      "window": "1-day"
    },
    "name": "kp_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNonow | 1-day (default) | 7-day | 1-minute

Output Schema

NameRequiredDescriptionDefault
kindNo
countNo
sourceNo
windowNo
cadenceNo
coverageNo
measurementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / window / description
      Previous value: -"1-day (default) | 7-day | 30-day | now"New value: +"now | 1-day (default) | 7-day | 1-minute"
    • addedOutput schema / properties
      Added value: +{
      +  "cadence": {
      +    "type": "string"
      +  },
      +  "count": {
      +    "type": "number"
      +  },
      +  "coverage": {
      +    "properties": {
      +      "newest": {
      +        "type": "string"
      +      },
      +      "oldest": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "kind": {
      +    "type": "string"
      +  },
      +  "measurements": {
      +    "items": {
      +      "properties": {
      +        "Kp": {
      +          "type": "number"
      +        },
      +        "a_running": {
      +          "type": "number"
      +        },
      +        "station_count": {
      +          "type": "number"
      +        },
      +        "time_tag": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "source": {
      +    "type": "string"
      +  },
      +  "window": {
      +    "type": "string"
      +  }
      +}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "window": "1-day"
      +  },
      +  {
      +    "window": "7-day"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Planetary K-index data in various time windows",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/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. The description adds substantial context beyond that: data freshness, estimated vs observed vs forecast values, row flags, feed lengths, and a retired-archive limitation.

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?

Front-loads the definition and scale, then gives structured window semantics and a source limitation. It is dense but every clause carries useful information.

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?

For a one-parameter data retrieval tool with an output schema, the description covers scale interpretation, window behavior, freshness, forecast vs observed distinctions, and the absence of long-range history. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema only lists window strings. The description adds real meaning to each window, including freshness, cadence, forecast inclusion, and the approximate lookback period.

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?

Clearly states the resource: NOAA planetary K-index, global geomagnetic activity on a 0-9 scale, with the storm threshold. It does not explicitly distinguish itself from sibling Kp or aurora tools, so it stops short of a 5.

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?

Explains what each window returns and its freshness/coverage limits: now, 1-day observed feed, 7-day observed plus forecast, and 1-minute last ~6 hours. It also notes the 30-day archive is unavailable, but does not explicitly route the agent to or away from sibling tools.

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.