Mappit

Map layer

get_map_layer

Read-onlyIdempotent

One of Mappit's live map layers, for a place or the whole world: earthquakes (USGS), wildfires (NASA FIRMS), air_quality and weather (Open-Meteo), history (events on this day in past years), stocks (S&P 500 companies by headquarters), events (public event pins) and radio_tv (live news radio and TV streams). For the whole world, air quality lists the worst readings first and weather the hottest.

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": {
      "layer": "<layer>"
    },
    "name": "get_map_layer"
  }
}

Input Schema

Name	Required	Description
`date`	No	For history and stocks: a date like "2026-09-28" (history uses its month and day). Default today.
`layer`	Yes	One of: earthquakes, wildfires, air_quality, weather, history, stocks, events, radio_tv.
`limit`	No	How many: default 20, at most 50.
`place`	No	Where: a place name, place id, country or "lat,lon". Omit for the whole world.
`radius_km`	No	Around a place, how far to look in km. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: whole-world result ordering for air_quality (worst readings first) and weather (hottest), which an agent cannot derive from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is front-loaded and readable, but roughly half the text restates the layer enum already present in the schema's layer description, which is wasted space. The trailing sentence about world-wide ordering is useful but tacked on rather than integrated.

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?

All five parameters are documented in the schema, annotations cover the safety profile, and the description explains the layer taxonomy. With no output schema, the description could say more about the shape of returned pins/readings, but for a self-explanatory read tool this is close to complete.

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 every parameter (date, layer, limit, place, radius_km) is already documented, and the baseline is 3. The description reinforces that 'place' can be omitted for the whole world, but that is already in the schema, and the ordering note is a result behavior rather than parameter semantics.

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 states the resource (Mappit's live map layers) and enumerates the concrete layer values with their data sources (USGS, NASA FIRMS, Open-Meteo), so an agent knows exactly what this tool returns. It does not explicitly differentiate itself from siblings like whats_happening or get_statistic, which also surface live data, so it falls 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 Guidelines3/5

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

Usage is only implied through the layer enumeration; there is no explicit 'use this when' statement and no alternative sibling is named or contrasted. The reader must infer that this is the tool for map-layer data versus the digest/story/statistic tools.

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

All Mappit tools Inspect

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

Need Help?