Skip to main content
Glama
Sign In
delian

ddflow

by delian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ddflow_show

Everything known about one phase, task, bug or research note: state, dependencies, globs, the lease holder, the worktree path, and every gate's outcome with evidence. Check your work with it before ddflow_complete.

Instructions

Everything known about one phase, task, bug or research note: state, dependencies, globs, the lease holder, the worktree path, and every gate's outcome with evidence. Check your work with it before ddflow_complete.

Input Schema

NameRequiredDescriptionDefault
idYesItem, bug or research-note id.
briefNoWith report: the 8-line form.
reportNoIts completion report.
as_agentNoSubagent name, this call only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.7
    • changedInput schema / properties / as_agent / description
      Previous value: -"A subagent's own name, this call only."New value: +"Subagent name, this call only."
    • addedInput schema / properties / brief
      Added value: +{
+  "description": "With report: the 8-line form.",
+  "type": "boolean"
+}
    • changedInput schema / properties / id / description
      Previous value: -"Item id (phase, task) or bug id."New value: +"Item, bug or research-note id."
    • addedInput schema / properties / report
      Added value: +{
+  "description": "Its completion report.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.1.12
    • changedInput schema / properties / as_agent / description
      Previous value: -"Subagent sharing the parent's connection: your own stable name, for this call only (see ddflow_identify)."New value: +"A subagent's own name, this call only."
  3. Changed2 schema fields changedv0.1.10
    • addedInput schema / properties / as_agent
      Added value: +{
+  "description": "Subagent sharing the parent's connection: your own stable name, for this call only (see ddflow_identify).",
+  "type": "string"
+}
    • changedInput schema / properties / id / description
      Previous value: -"Item id."New value: +"Item id (phase, task) or bug id."
  4. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it discloses the breadth of returned data (including lease holder and gate evidence) which implies a rich read, but never states explicitly that the call is read-only or side-effect free. The as_agent parameter ('this call only') hints at scoped impersonation without explaining authorization implications.

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?

Two sentences, zero filler. The returned-data enumeration comes first (front-loaded payoff) and the single actionable directive follows immediately.

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?

No output schema exists, so the description does real work by enumerating what comes back (state, dependencies, globs, lease, worktree, gate outcomes). Remaining gaps are minor: no sense of response size or whether large evidence payloads need brief/report toggling, and no explicit read-only statement.

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 four parameters are already documented in the schema; the baseline is 3. The description adds no extra meaning about how 'report' and 'brief' interact or when to set as_agent, so it neither compensates nor detracts.

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 description uses a specific framing ('Everything known about one phase, task, bug or research note') and enumerates the exact fields returned: state, dependencies, globs, lease holder, worktree path, gate outcomes with evidence. That clearly separates it from mutation siblings like ddflow_update or ddflow_complete, though it never names the closest read siblings (ddflow_brief, ddflow_flow_show, ddflow_gate_status) to disambiguate.

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?

'Check your work with it before ddflow_complete' gives one concrete trigger and names the alternative workflow step it precedes. It lacks any when-not guidance (e.g., use ddflow_list to discover ids, or ddflow_brief for a shorter view), so routing is helpful but not exhaustive.

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