Skip to main content
Glama
Sign In

GeoSpark

by io.github.Maz2580
OverviewDiscussionsAdmin

Active fires

get_active_fires
Read-onlyIdempotent

Satellite active-fire detections near a point (NASA FIRMS; the server needs a FIRMS_MAP_KEY).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_active_fires"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to look for detections
latitudeYesLatitude in degrees (WGS84)
longitudeYesLongitude in degrees (WGS84)

Output Schema

NameRequiredDescriptionDefault
queryNo
unitsNoUnit of each numeric field
statusNook
channelYes
featuresYesRecords from the data source
warningsNoCaveats to tell the user
provenanceNoSource, licence, attribution, retrieval time and method
total_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / days / description
      Added value: +"How many days back to look for detections"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, open-world), so the description's marginal contribution is the FIRMS_MAP_KEY server credential requirement and the NASA FIRMS provenance, both of which affect whether a call will succeed at all. It stops short of describing the spatial search radius or detection-confidence caveats that would matter for interpreting a result.

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?

One front-loaded sentence with zero filler; the data source and credential prerequisite are packed into a short parenthetical rather than a separate clause. Nothing is redundant with the title.

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?

An output schema exists, so return shape needn't be explained, and the params are well covered by the schema. However, with no radius parameter, the description leaves the spatial extent of "near a point" completely undefined, and it doesn't note that satellite hot-spot detections may be false positives — a material gap for interpreting results.

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 latitude, longitude and the 1-2 day lookback window are already fully documented in the schema. The description adds only provenance context, not any new meaning about units, precision, or how the point defines the search area.

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?

"Satellite active-fire detections near a point" gives a concrete resource (fire detections) and a specific scope (near a point), and names the upstream source (NASA FIRMS). This distinguishes it clearly from the weather/air-quality siblings, though it never names an alternative tool by name.

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?

Usage is only implied: an agent infers it should call this when asked about fires near a coordinate. There is no explicit when-to-use or when-not-to-use guidance, and nothing says whether this is preferable to a generic overture_features or location_report query for the same question.

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

All GeoSpark toolsInspect
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