Skip to main content
Glama
Sign In
agent-pool-mcp

agent-pool-mcp

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

signal_step_complete

Notify the orchestrator that a specific pipeline step has finished execution, allowing the workflow to proceed.

Instructions

Signal that a pipeline step is complete (called BY agents running inside pipeline steps).

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": {
      "step_name": "<step_name>"
    },
    "name": "signal_step_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to current working directory.
jsonNoReturn pure JSON string instead of Markdown format.
outputNoOptional output message or result.
run_idNoPipeline run ID for precise targeting. Provided in the task prompt.
step_nameYesName of the completed step.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.3

TDQS

A3.9/5.0
Behavior3/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 the tool signals step completion, but does not describe side effects, required permissions, or what happens after signaling. For a simple signaling tool, this is adequate but not thorough.

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?

A single 14-word sentence that efficiently conveys purpose and caller context. No extraneous information.

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

Completeness3/5

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

No output schema is present, and the description does not mention return values or error behavior. With 5 parameters (1 required) and no annotations, more details on expected outcomes would improve completeness, but the core function is clear.

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 parameters are documented in the schema. The description does not add additional meaning beyond the schema. 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?

The description clearly states the verb 'signal', the resource 'pipeline step', and importantly specifies the caller context: 'called BY agents running inside pipeline steps'. This distinguishes it from sibling tools like 'get_pipeline_status' or 'cancel_pipeline'.

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?

The description explicitly states that this tool is called by agents inside pipeline steps, providing clear usage context. Although it doesn't list alternatives or when not to use it, the context is specific enough to guide correct invocation.

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