Skip to main content
Glama

ingest_plan

Push a saved plan into Plane by creating epics and linked issues, optionally limiting to selected epic summaries, and return a manifest mapping local IDs to Plane UUIDs.

Instructions

Push a saved plan into Plane. Creates epics first, then issues linked to their parent epic. Optionally restrict to specific epic summaries via only_epics. Returns a manifest mapping local IDs to Plane UUIDs.

Re-ingesting an already-ingested plan merges into the existing manifest rather than replacing it: epics/stories not touched this call (including everything only_epics excludes) are preserved verbatim, a story whose key already exists gets its authored fields (summary, agent_instructions, dependencies, persona, model, acceptance, risk (only while todo), backend, tdd_split, files, blocked_by, test_scope) refreshed while its runtime state (status, pr_url, escalated, ...) is kept, and top-level manifest keys outside epics/stories/repo_root (paused, local_model_fallback, final_rework_escalation, ...) carry over untouched. Pass overwrite=True to restore the old wholesale-replace behavior (drops anything not produced by this call).

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>"
    },
    "name": "ingest_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
overwriteNo
plan_nameYes
only_epicsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that re-ingest merges rather than replaces, lists which authored fields get refreshed versus which runtime state (status, pr_url, escalated) is preserved, and states exactly what overwrite drops. Missing is any mention of failure modes, permissions/auth needed to reach Plane, or whether a partial ingest is rolled back.

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?

Purpose and the critical merge-vs-overwrite distinction are front-loaded in the first paragraph, with the detailed field-preservation rules deferred. The dense parenthetical field lists (tdd_split, blocked_by, test_scope, ...) are heavy but each carries real behavioral information, so little is wasted.

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?

An output schema exists, so the manifest return value does not need elaboration beyond the one-line mention it gets. For a three-parameter mutation tool with no annotations, the merge semantics are unusually well covered; the remaining shortfall is the unexplained plan_name and absent error/precondition behavior.

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 description coverage is 0%, so the description must compensate and largely does: only_epics is explained as restricting to specific epic summaries, and overwrite is tied to an explicit semantic change (wholesale replace vs merge). plan_name is the one gap — it is required but never explained, leaving its origin or format unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource — push a saved plan into Plane — and immediately states the internal ordering (epics first, then linked issues). That distinguishes it from save_plan/decompose_plan in this catalog. It does not name a sibling explicitly, so it falls short of a 5.

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 makes clear this is the ingest/mutation step for an already-saved plan and gives an explicit switch condition: pass overwrite=True to restore wholesale-replace behavior. What it omits is any prerequisite statement (e.g. that the plan must already exist via save_plan) or guidance on when to prefer patch_plan for incremental edits.

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