Skip to main content
Glama

TeamShared

by io.github.xhad
OverviewDiscussionsAdmin

process_run_get

Fetch one Process run (snapshot, current step, standing, work, stream_id).

standing is a projection over run:{id} events (true / changed / next / owner / blocked / since / due / timeout). It is not a writable column — draft with process_run_standing_draft and commit with process_run_standing_commit. Pass source=events to fold the run object from the log alone (no process_runs read).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesProcess run UUID
sourceNorow (default) reads process_runs; events reconstructs the run from stream_events on run:{id} only

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / source
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "row (default) reads process_runs; events reconstructs the run from stream_events on run:{id} only"
+}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that standing is a projection over events, is not writable, and explains the source parameter's behavior. It also lists the fields returned. This is substantial and helpful, though it could mention potential errors or authorization needs, but for a read tool this is adequate.

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 concise and well-structured. The first line states the main purpose, followed by a crucial explanation of standing and the source parameter. No unnecessary fluff; every sentence adds value.

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?

There is an output schema (though not shown), and the description explains the key behavioral aspects: what standing is, how to use source, and what the run contains. It does not cover error handling or permissions, but given the presence of an output schema, the essential information is present. It is complete enough for correct invocation.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema: it clarifies what source=events does (reconstructs from log only) and explains the nature of standing as a projection. This is valuable context that the schema alone does not provide.

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 clearly states a specific verb and resource: 'Fetch one Process run' and enumerates the fields returned (snapshot, current step, standing, work, stream_id). It distinguishes itself from sibling tools like process_run_list and process_run_events by focusing on a single run and explicitly calling out the standing projection, which is a unique concept.

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

Usage Guidelines5/5

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

It explicitly explains the source parameter ('Pass source=events to fold the run object from the log alone') and clarifies when to use this vs. the draft/commit tools for standing (standing is not writable, use process_run_standing_draft/commit). This gives clear guidance on selection and alternatives, even naming specific siblings.

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

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