Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap

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. Wiping a filter chain is recoverable via undo, but autonomous agents lack a UI surface to confirm intent.
rationaleYesShort 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.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations provide idempotentHint=true and destructiveHint=false. The description adds important behavioral context: the gated mechanism requiring confirmation, recoverability via undo, and the no-op behavior. No contradiction with annotations.

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?

The description is two concise sentences plus a brief note, front-loading the core action. Every sentence adds value, with no wasted words.

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?

Given the tool's simplicity and absence of output schema, the description covers the main behavior, gating, and relationship to filter_layer. It could optionally detail the success return value, but the current content is adequate for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (2 of 4 parameters have descriptions). The description does not add meaning for map_id or layerId beyond the schema, and it only echoes the schema for confirmed and rationale. It does not compensate for the undocumented parameters.

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 uses specific verbs ('Wipe every predicate', 'making every source feature visible again') and clearly identifies the resource as a layer's filter chain. It distinguishes itself by stating it is the inverse of filter_layer and clarifies it is a no-op on layers with no filters.

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?

The description explicitly contrasts with filter_layer (inverse) and notes the no-op case. It explains the gated behavior (confirmed parameter) but does not provide explicit when-not-to-use guidance beyond that.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but a few pairs such as select_within/focus_area and correlate_layers/add_fusion_layer overlap in function, differing mainly by input type or output (read vs. write). The descriptions adequately explain these differences, so agents can distinguish them with careful reading.

Naming Consistency5/5

Tool names consistently follow a verb_noun snake_case pattern (add_layer, filter_layer, export_image, remove_annotation). Minor exceptions like undo/redo/tag are conventional single verbs and do not detract from the overall predictability.

Tool Count4/5

At 25 tools, the server is on the heavy side, but each tool serves a distinct operation in a comprehensive mapping workspace—covering creation, editing, analysis, export, and history. The number feels justified by the broad feature set rather than excessive.

Completeness4/5

The toolset covers the full lifecycle of layers and workspace state, including add/remove/rename/restyle/filter, build/get/mutate/undo/redo, export, and tagging. Minor gaps such as annotation editing, layer reordering, or direct data updates exist, but they are not critical blockers for typical workflows.

Resources