Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap
OverviewDiscussionsAdmin

Report a blocker (agent feedback)

report_blocker

Send the ShowMeOnMap team a report about a request this server could not complete — an unsupported intent, a missing tool, an unclear schema, or an op that failed in a confusing way. Records the report to a server-side log for future capability work; it does not change the current map or session. map_id is optional, so a report can be filed before any map exists.

Input Schema

NameRequiredDescriptionDefault
map_idNoOptional. The map_id you were working on, if any.
rationaleNoOptional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
what_i_triedYesWhich tools / inputs you attempted, in order. Be specific — tool name + key arg shape is ideal.
what_i_was_tryingYesHigh-level intent in one or two sentences. e.g. "merge two filtered choropleths into a fused bivariate map".
where_i_got_stuckYesThe specific failure: what came back, what was missing, why you could not proceed.
suggested_capabilityNoOptional. A new tool, op, or schema field that would have unblocked you.

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: -[
-  "what_i_was_trying",
-  "what_i_tried",
-  "where_i_got_stuck",
-  "rationale"
-]New value: +[
+  "what_i_was_trying",
+  "what_i_tried",
+  "where_i_got_stuck"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / rationale
      Added value: +{
+  "description": "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.",
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "what_i_was_trying",
-  "what_i_tried",
-  "where_i_got_stuck"
-]New value: +[
+  "what_i_was_trying",
+  "what_i_tried",
+  "where_i_got_stuck",
+  "rationale"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and non-idempotent, and the description adds real context beyond them: the report is written to a server-side log for future capability work and does not mutate the map or session. It does not address whether repeated submissions duplicate the log entry (relevant given idempotentHint=false) or any rate limits, which keeps it below a 5.

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 sentences, all load-bearing: the first defines the tool and its trigger conditions, the second states the side effect and the non-effect, the third handles the optional parameter. Nothing is redundant and the most important information is front-loaded.

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 6-parameter write tool with no output schema, the description covers purpose, trigger, side effects, and the optional map_id, which is enough to call it correctly. It omits any mention of what the caller sees back (e.g., a confirmation or report id), which is a minor gap with no output schema to fall back on.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine meaning for map_id: it explains that the parameter is optional and why ('a report can be filed before any map exists'), which the schema only states as 'Optional.' The remaining parameters are left entirely to the schema.

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 ('Send the ShowMeOnMap team a report') and enumerates exactly what qualifies as a blocker: unsupported intent, missing tool, unclear schema, confusing failure. This cleanly distinguishes it from every sibling, which are all map/session mutators or readers.

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?

Gives clear context for when to invoke it (a request the server could not complete) and enumerates four qualifying failure categories, plus a when-not clause ('it does not change the current map or session'). It does not name any alternative tool or say when to prefer other error paths, so it falls short of an explicit alternatives statement.

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