Skip to main content
Glama
Sign In

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Advance Workflow

advance_workflow
Destructive

Advance a workflow past a human checkpoint — approve or reject the paused step so the pipeline continues. Use the session id from run_workflow / get_workflow_session. Requires authentication.

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": {
      "session_id": "<session_id>",
      "action": "<action>"
    },
    "name": "advance_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional reviewer notes recorded with the decision.
actionYesExplicit checkpoint decision: 'approve' or 'reject'.
session_idYesThe workflow session id (must be awaiting a checkpoint).
expected_step_idNoFor routed workflows, the paused result step_id returned by get_workflow_session.
expected_execution_seqNoFor routed workflows, the paused result execution_seq returned by get_workflow_session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changed
    • addedInput schema / properties / expected_execution_seq
      Added value: +{
+  "description": "For routed workflows, the paused result execution_seq returned by get_workflow_session.",
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / expected_step_id
      Added value: +{
+  "description": "For routed workflows, the paused result step_id returned by get_workflow_session.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is partly carried structurally. The description usefully adds that auth is required and that the call resumes a paused pipeline, but it never explains the destructive side (e.g. that 'reject' terminates/abandons the step or that the action is not repeatable) — the most important behavioral caveat for this tool.

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?

Two tight sentences, zero filler, with the core action front-loaded before the session-id sourcing and auth note.

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 non-idempotent, destructive, authenticated mutation with no output schema, the description covers purpose, checkpoint precondition, parameter provenance, and auth. The one gap is the consequence of a reject decision and any irreversibility, which an agent deciding between approve/reject would benefit from.

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 would be 3. The description goes beyond the schema by stating where session_id comes from (run_workflow / get_workflow_session) and that the session must be checkpoint-paused, which is real operational meaning the schema does not supply.

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?

Specific verb ('advance') plus resource ('workflow') plus the exact semantic moment ('past a human checkpoint — approve or reject the paused step'). Clearly distinguishable from run_workflow, retry_workflow, and get_workflow_session in the sibling list.

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?

Tells the agent to use the session id from run_workflow / get_workflow_session and that the session must be paused at a checkpoint, which is clear situational guidance. It stops short of explicitly contrasting with retry_workflow or decide_approval, so no when-not guidance.

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

All Meta Council 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