Skip to main content
Glama

TeamShared

by io.github.xhad
OverviewDiscussionsAdmin

process_run_advance

Advance a Process run after the current step is finished.

Illegal when the run is completed/cancelled, finished_step is not the current step, or the process is unknown. A template step that requires evidence refuses with evidence_missing until it is attached (evidence_attach).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoOverride agent attribution label
run_idYesProcess run UUID
finished_stepYesStep the accountable seat just finished (must match current_step)
evidence_overrideNoSigned-in org admins only: why to advance although the step's required evidence is missing. Logged as evidence.override.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / evidence_override
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Signed-in org admins only: why to advance although the step's required evidence is missing. Logged as evidence.override."
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses refusal conditions, the evidence gate, and the logged evidence.override side effect. It falls short of describing the post-advance effects (e.g., whether a step event is emitted or the next step is activated), which matters for a state-machine mutation.

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 tight sentences: the action first, then preconditions, then the evidence exception. No filler and no repetition of the schema.

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?

An output schema exists so return values need not be explained, and failure modes are well covered. The one gap is the absence of any statement about downstream effects of a successful advance in a multi-step run workflow.

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 description coverage is 100%, so all four parameters are already documented in the schema, including evidence_override's admin-only constraint. The description adds no syntax or format detail beyond naming evidence_attach, so the baseline 3 is appropriate.

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 (Advance) and resource (a Process run) with a precise trigger condition ('after the current step is finished'). An agent can distinguish this from siblings like process_run_complete or process_run_step_fail based on the vocabulary of 'advance' vs 'complete'/'fail'.

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?

Explicitly enumerates the when-not cases (run completed/cancelled, finished_step mismatch, unknown process) and the evidence gate, and names the alternative action (evidence_attach) needed before retrying. This is exactly the routing information an agent needs.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources