Skip to main content
Glama
Sign In

WebArm24

by online.webarm24
OverviewDiscussionsAdmin

workflow_run_get

Run status (running|waiting|ok|error|cancelled), node_states (per node: status, run_id of the inner pipeline run, preview, error, port taken, for_each iterations), output_preview.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow_id": "<workflow_id>",
      "run_id": "<run_id>"
    },
    "name": "workflow_run_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
workflow_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only describes return fields. It does not state that this is a read-only operation, whether it requires permissions, or what happens on invalid or missing runs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but structured as a fragmented list of output fields rather than a front-loaded action statement. It is under-specified for an agent deciding how to invoke the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It partially compensates for the missing output schema by listing top-level return fields and node_states details. However, it omits input parameter meaning, usage context, and behavioral traits needed for correct invocation.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain the required workflow_id or run_id inputs. The only mention of run_id refers to the inner pipeline run within node_states, not the input parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists what the tool returns (status, node_states, output_preview) rather than stating a clear action like 'Get details of a workflow run.' It implies retrieval but does not distinguish the tool from siblings such as workflow_run, workflow_runs_list, or pipeline_run_get.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The description does not mention workflow_run, workflow_runs_list, or pipeline_run_get, nor does it indicate prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WebArm24 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