Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap
OverviewDiscussionsAdmin

Build a map

build_map

Make an interactive, data-driven map from a plain-language request, built from live public data with every value cited to its source. Covers natural hazards (earthquakes, wildfires, volcanoes, tropical storms, floods), weather and air quality, statistics by country, state or region (GDP, population, health, emissions — World Bank, Eurostat, US Census), infrastructure and transit (railways, power plants, transit lines, roads), parks and terrain, and points of interest from OpenStreetMap. The query carries the place, time window and any thresholds — "earthquakes above magnitude 5 near Japan this month", "GDP per capita across Europe" — and the server applies them itself. Returns a shareable link and a map_id for follow-ups (mutate_map, filter_layer, get_state); in clients that support MCP Apps the map also renders interactively in the conversation. Analysis maps (site selection, spatial analysis) can take one to three minutes: when the build outlasts one call it returns status "building" with a resume_token, and calling build_map again with the same query and that resume_token collects the map without spending credits. The Op catalog and predicate grammar that downstream tools (mutate_map, filter_layer, etc.) accept are documented in the MCP resource showmeonmap://docs/workspace-ops-spec.

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language: "coffee shops in Tokyo", "GDP by country", "volcanoes in Indonesia", etc.
rationaleNoOptional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
resume_tokenNoOnly when a previous build_map returned status "building": its resume_token, to collect that map. Collecting spends no credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resume_token
      Added value: +{
+  "description": "Only when a previous build_map returned status \"building\": its resume_token, to collect that map. Collecting spends no credits.",
+  "pattern": "^[a-f0-9]{32}$",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / rationale / description
      Previous value: -"Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. \"add wildfire layer for the user's California query\". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history."New value: +"Optional short label (≤300 chars) for the map edit history, e.g. \"add wildfire layer\". Omit it to send nothing beyond the tool arguments."
    • changedInput schema / required
      Previous value: -[
-  "query",
-  "rationale"
-]New value: +[
+  "query"
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

While the annotations are basic, the description provides substantial behavioral context not explicitly covered by the schema. It details that analysis maps may take 1-3 minutes, how it signals progress ('building'), and the mechanism for resuming the job using a 'resume_token' without further credits. This is high-value behavioral information.

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 quite long, but every sentence provides necessary value and structure. It is front-loaded with the core functionality and follows up with important operational details, making the density high, even if length is a minor concern.

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?

The description is extremely complete for this type of complex, asynchronous tool. It details data sources, output mechanisms (shareable link, map_id, interactive render), and the complete workflow for long-running tasks and follow-ups (mutate_map, filter_layer), giving an agent everything needed.

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?

Since schema coverage is 100%, the description needs to add high-level context, which it does brilliantly by defining what the input 'query' can contain (place, time, thresholds) and defining the specific purpose of the optional 'rationale' and 'resume_token' fields beyond their data types.

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 clearly defines the tool's purpose: creating interactive, data-driven maps. It distinguishes its function by specifying that it processes plain-language requests, deals with a wide range of topics (hazards, GDP, infrastructure, etc.), and uses live public data while citing sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It provides clear usage context for several scenarios: using natural language queries, utilizing the optional 'rationale' for edit history, and specifically using the 'resume_token' if the initial request runs long. It also preemptively guides users to the MCP resource for detailed syntax regarding sibling tools.

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

All ShowMeOnMap 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