Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap
OverviewDiscussionsAdmin

Run a saved workflow

run_workflow

Execute a saved workflow with parameter values. PAID: bills ~1 credit per step through the normal build/mutate paths (the estimate is in list_workflows). Optional batch mode sweeps ONE param across 2–20 values — each value is a full independent run (steps × values credits); failed/paused values are reported per value and the batch continues. A clarification pauses a single run (status "paused" + the question); failures stop at the failing step. On success the result is a live map with a shareable URL (batch: the last successful value's map).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batchNoBatch mode: run the workflow once per value ("each of the 12 districts"). Bills steps × values.
paramsNoValues for the workflow's declared parameters.
rationaleNoOptional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.
workflow_idYesFrom save_workflow or list_workflows.

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: -[
-  "workflow_id",
-  "rationale"
-]New value: +[
+  "workflow_id"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / batch
      Added value: +{
+  "description": "Batch mode: run the workflow once per value (\"each of the 12 districts\"). Bills steps × values.",
+  "properties": {
+    "param": {
+      "description": "The ONE declared param to sweep (must not also be in params).",
+      "minLength": 1,
+      "type": "string"
+    },
+    "values": {
+      "description": "2–20 values; each is a FULL independent billed run.",
+      "items": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 20,
+      "minItems": 2,
+      "type": "array"
+    }
+  },
+  "required": [
+    "param",
+    "values"
+  ],
+  "type": "object"
+}
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations (readOnly=false, destructive=false, idempotent=false): billing (~1 credit/step, batch bills steps × values), clarification pauses a single run with status "paused", failures stop at the failing step while batch continues per value, and the success result is a live map with a shareable URL. These are exactly the operational traits an agent cannot infer from annotations.

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?

Purpose is front-loaded and every sentence carries operational weight (billing, batch, pause, failure, return). It is dense and slightly packed into one paragraph, but there is little redundancy.

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 4-param tool with a nested batch object and no output schema, the description is thorough: it documents billing, batch semantics, failure/pause handling, and the returned live map/URL. It omits auth/permission requirements and how to resume a paused run, leaving minor gaps.

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 100%, so baseline is 3. The description's batch explanation (sweep ONE param, 2-20 values, each a full run) largely restates what the schema's batch.param and batch.values descriptions already state, adding only marginal detail.

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 ("Execute a saved workflow with parameter values") and names list_workflows as the source of the cost estimate, clearly separating it from save_workflow/list_workflows. An agent immediately knows this runs an existing workflow rather than creating or enumerating one.

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 operating context: batch mode is for sweeping ONE declared param across 2-20 values, and the estimate lives in list_workflows. It does not, however, explicitly contrast run_workflow with build_map/mutate_map or state when-not to use it, so it falls short of a full when/when-not/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