Skip to main content
Glama

unblock_story

Unblocks a parked story by clearing retry or review fields, recording the manual intervention, and optionally updating status, files, or instructions under the plan lock.

Instructions

Unblock a parked story, recording the manual intervention.

Authorized like set_story_status (the plan's owner or a delegate; anyone else is refused). Clears the named retry/review fields, optionally sets status and appends add_files to the story's files, exactly as python -m pipeline.unpark does, and records the caller as the human action. All of it happens under the plan lock.

plan_name / story_key: the parked story. clear_fields: names to delete; only the retry counters and review records in pipeline.unpark.UNPARKABLE_FIELDS are accepted. status: one of the statuses the pipeline assigns (default: unchanged). add_files: repo-relative production paths (no leading '/', no backslash, no NUL, no '..') appended to the story's files. note: up to 8000 characters appended to the story's agent_instructions. It is written together with the unblock notice, or not at all.

Changing the brief or files resets the plan's approval exactly as patch_story does; the result says so with approval_reset. A refused value is never echoed. If the plan lock is busy the result carries skipped: "locked" and retry_after_seconds: call again.

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": {
      "plan_name": "<plan_name>",
      "story_key": "<story_key>",
      "clear_fields": "<clear_fields>"
    },
    "name": "unblock_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
statusNo
add_filesNo
plan_nameYes
story_keyYes
clear_fieldsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it names the authorization model (plan owner or delegate, others refused), the concrete mutations (deleting UNPARKABLE_FIELDS, optional status, file/note appends), the side effect of resetting plan approval, the refusal non-echo guarantee, and lock-contention behavior with the literal `skipped: "locked"` and `retry_after_seconds` payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the action, then organizes parameters as a labeled block followed by cross-cutting semantics (approval reset, refusals, locking), so it reads well despite its length. A few phrases such as 'exactly as python -m pipeline.unpark does' lean on external context, but nearly every sentence carries operational information.

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 six-parameter mutation tool with no annotations, the description covers authorization, mutation scope, side effects, error and retry semantics, and even cross-references the result keys (approval_reset, skipped, retry_after_seconds) beyond what the output schema alone would convey. Nothing an agent needs to invoke it correctly appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all six parameters, and it largely does: clear_fields is bounded to UNPARKABLE_FIELDS, status is constrained to pipeline-assigned values with the unchanged default noted, add_files gets explicit path validation rules (no leading '/', backslash, NUL, or '..'), and note gets an 8000-character limit plus its target field and atomic-write guarantee.

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 and resource ('Unblock a parked story') plus the recording of the manual intervention, which is the distinguishing side effect. It explicitly aligns itself with set_story_status for authorization and patch_story for approval-reset semantics, so an agent can place it precisely among the many story_* siblings.

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 trigger condition is clear from 'parked story' and the retry/review field clearing, and it names set_story_status and patch_story as behavioral reference points. It never states an explicit exclusion or a 'use X instead when...' rule, so routing is inferable rather than spelled out.

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