Skip to main content
Glama
Sign In
junai-mcp

junai-mcp

by saajunaid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

skip_stage

Skip the current pipeline stage and advance to the next one when the stage is unnecessary, auto-approving gates the skipped stage would have satisfied.

Instructions

Skip the current pipeline stage and advance to the next one.

Use when a stage is not needed for this task (e.g. skipping security review for a docs-only change, or skipping prd for a small bug fix). Only the current stage can be skipped. Gates that the skipped stage would have satisfied are auto-approved.

Returns the result including new current_stage and progress_line.

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_to_skip": "<stage_to_skip>",
      "reason": "<reason>"
    },
    "name": "skip_stage"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
stage_to_skipYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.18

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that gates are auto-approved for skipped stages and describes the return result including current_stage and progress_line, but lacks details on side effects.

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 very concise (5 sentences), front-loaded with the main action, and uses clear examples without unnecessary fluff.

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?

Given the presence of an output schema, the description adequately covers the tool's effect and return value, but could mention irreversibility or constraints like 'must be current stage' (already implied).

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 has 0% description coverage, and the description adds some context (e.g., reason for skipping) but does not explicitly define expected values for stage_to_skip or fully describe the reason parameter.

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 action ('Skip the current pipeline stage and advance to the next one') and the resource, distinguishing it from siblings like replay_stage or satisfy_gate.

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?

Provides explicit when-to-use examples (e.g., skipping security review for docs-only change) and notes that only the current stage can be skipped, but does not explicitly list when not to use it.

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