Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap
OverviewDiscussionsAdmin

Set the time window (direct)

set_time
Idempotent

Override the current time-range filter. Latest set_time op wins during replay. Covers requests like "filter to 2020-2024" or "show only the last 7 days". Not yet consumed by the renderer — the UI drives the slider directly — but the value is captured in the ops log and queryable via get_state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYesFeature property carrying the time value (e.g. "date", "year", "timestamp").
formatNoHow rangeStart/rangeEnd encode time. Default: unix_ms at render time.
map_idYes
rangeEndYesInclusive upper bound of the visible window.
rationaleNoOptional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
rangeStartYesInclusive lower bound of the visible window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: -[
-  "map_id",
-  "field",
-  "rangeStart",
-  "rangeEnd",
-  "rationale"
-]New value: +[
+  "map_id",
+  "field",
+  "rangeStart",
+  "rangeEnd"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses genuinely non-obvious behavior: the value is not yet consumed by the renderer and instead lands in the ops log where it is retrievable via get_state. That is materially useful state-effecting context the readOnly/destructive/idempotent hints cannot convey.

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 the core action and followed by ordering semantics and the renderer caveat. Every sentence carries distinct information with no padding.

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?

For a mutation tool with no output schema, the description covers the core action, overwrite/replay semantics, and where the value ends up. The main omission is any explicit routing against alternative filter tools.

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 coverage is 83%, so the schema already documents field, rangeStart/rangeEnd, format, and rationale in detail. The description only alludes to the time range generically and adds no syntax or format guidance beyond what the schema provides, so the baseline 3 applies.

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 a specific verb+resource: 'Override the current time-range filter,' matching the title's 'set the time window.' It is clearly distinct from neighboring tools like clear_filters or query_features, though it never names a sibling directly to sharpen that contrast.

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 supplies trigger phrases ('filter to 2020-2024', 'show only the last 7 days') and a replay-ordering rule ('latest set_time op wins'), which is real usage context. However it gives no when-not guidance and never contrasts against clear_filters or filter_layer, so the agent must infer the boundary.

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