Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap
OverviewDiscussionsAdmin

Clear all filters on a layer (direct, gated)

clear_filters
Idempotent

Wipe every predicate currently applied to a layer's filter chain, making every source feature visible again. Inverse of filter_layer. No-op on layers that have no existing filter. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
map_idYes
layerIdYes
confirmedNoSet to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. A cleared filter chain can be restored with undo.
rationaleNoOptional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirmed / description
      Previous value: -"Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Wiping a filter chain is recoverable via undo, but autonomous agents lack a UI surface to confirm intent."New value: +"Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. A cleared filter chain can be restored with undo."
  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: -[
-  "map_id",
-  "layerId",
-  "rationale"
-]New value: +[
+  "map_id",
+  "layerId"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description adds real context beyond them: the confirmation gate (pass confirmed:true or receive a needs_confirmation envelope) and the no-op behavior on unfiltered layers. It does not describe the return shape, but the gating and idempotency/no-op disclosure is meaningful added value.

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?

Three tight sentences, each earning its place: operation+scope first, sibling relationship second, edge case and gate last. No filler or restatement of the name.

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?

Mutable tool with no output schema; the description covers the gate, the no-op case, and the inverse relationship, and the schema's confirmed description notes undo restorability. An agent has what it needs to invoke correctly, though the return envelope details beyond needs_confirmation are left implicit.

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 50%: confirmed and rationale are documented in the schema, while map_id and layerId are bare. The description reinforces the confirmed gate ('pass confirmed:true to proceed'), adding meaning for the most consequential parameter, but it does not clarify the two required identifier params, so it only partially compensates for the coverage gap.

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?

States a specific verb+resource ('wipe every predicate... on a layer's filter chain') and the resulting state ('making every source feature visible again'), then explicitly positions itself as the 'Inverse of filter_layer.' An agent can distinguish it from the sibling filter_layer without opening either schema.

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

Usage Guidelines4/5

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

Names the inverse operation (filter_layer) and clarifies the no-op case ('No-op on layers that have no existing filter'), which tells the agent when a call is redundant. It doesn't state a hard when-not-to-use condition beyond the no-op, so it falls short of explicit alternatives/exclusions.

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