Skip to main content
Glama

BRAINIAC Geo & Environment Lookups

List nearby NASA FIRMS fire hotspots

geo-environment_fire-hotspots-nearby
Read-onlyIdempotent

List MODIS C6.1 active-fire detections within a radius from the vendored 7-day FIRMS snapshot. Price $0.03 USDC. POST /api/v1/geo-environment/fire-hotspots-nearby. An unpaid call returns the x402 payment terms and does not run.

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>",
      "radiusKm": "<radiusKm>"
    },
    "name": "geo-environment_fire-hotspots-nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoto, string. Optional.
fromNofrom, string. Optional.
limitNolimit, integer, from 1 to 500. Required.
latitudeYeslatitude, number, from -90 to 90. Required.
radiusKmYesradiusKm, number, from 0.1 to 500. Required.
longitudeYeslongitude, number, from -180 to 180. Required.
minConfidenceNominConfidence, number, from 0 to 100. Optional.

Output Schema

NameRequiredDescriptionDefault
countNocount. Number.
windowNowindow. Object.
sourcesNosources. Array.
detectionsNodetections. Array.
snapshotAtNosnapshotAt. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds behavior those annotations cannot express: the data source is a vendored 7-day snapshot (so results are bounded in time and possibly stale), the invocation costs $0.03 USDC, and an unpaid call short-circuits to x402 payment terms rather than executing.

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?

Three short sentences, front-loaded with what the tool returns, followed by cost and the payment fallback. Every sentence carries information, though the raw endpoint path is more boilerplate than decision-relevant detail.

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?

With an output schema present and full parameter coverage, the description need not describe return values. It covers source, temporal bound, cost and payment behavior; the remaining gap is that it never reconciles the user-supplied from/to range with the fixed 7-day snapshot, which is the one thing an agent could get wrong.

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 baseline is 3. The description clarifies the spatial filter semantics of 'radius' but does not explain how the optional from/to date parameters interact with the fixed 7-day snapshot window, nor does it clarify the limit/confidence filtering beyond what the schema already states.

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 a specific verb and resource ('List MODIS C6.1 active-fire detections') and bounds the scope ('within a radius from the vendored 7-day FIRMS snapshot'), so an agent can distinguish it from the earthquake, GTFS, sun-times and demographics siblings without opening any schema.

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?

It gives one genuinely useful usage precondition ('An unpaid call returns the x402 payment terms and does not run'), which stops an agent from mistaking a payment challenge for a result. However, it offers no explicit when-to-use / when-not-to-use guidance or comparison to any alternative, leaving selection to be inferred from the resource description.

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.

Resources