Skip to main content
Glama
Sign In
junai-mcp

junai-mcp

by saajunaid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

replay_stage

Reset a stage to re-execute it without clearing the pipeline. Preserves notes and logs reasons; requires supervised mode and no completed downstream stages.

Instructions

Reset a single stage to not_started for re-execution without clearing the pipeline.

Only available in supervised mode — too risky for autopilot/assisted. Cannot replay a stage if a downstream stage has already completed (must replay the chain from that point).

Preserves _notes for continuity. Increments the stage's retry_count. Writes a record to _notes._replay_log[].

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": {
      "stage_name": "<stage_name>",
      "reason": "<reason>"
    },
    "name": "replay_stage"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy the replay is needed.
stage_nameYesThe stage to replay (e.g. 'implement', 'tester').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.18

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, so description fully discloses side effects: preserves _notes, increments retry_count, writes to _notes._replay_log[], and the downstream constraint.

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?

Four sentences, front-loaded with the main action, then constraints, then effects. Every sentence adds value with no redundancy.

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

Completeness5/5

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

For a tool with 2 required parameters and an output schema, the description covers purpose, usage, constraints, and side effects completely.

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% and schema descriptions already explain both parameters. The description adds little beyond the schema, only providing a slight example for stage_name and noting reason is logged.

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 the tool resets a single stage to not_started for re-execution without clearing the pipeline, distinguishing it from siblings like skip_stage and pipeline_reset.

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 states it is only available in supervised mode and cannot be used if a downstream stage has completed, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools