Skip to main content
Glama
Sign In
delian

ddflow

by delian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ddflow_help

What ddflow IS, what it can do, and what the workflow is. Call this first if you have not used it before: the other descriptions explain one tool each and the connection instructions describe THIS repository; neither answers 'how am I…

Instructions

What ddflow IS, what it can do, and what the workflow is. Call this first if you have not used it before: the other descriptions explain one tool each and the connection instructions describe THIS repository; neither answers 'how am I meant to work here'. No argument: the loop from picking work to landing it, the exit codes, and every capability grouped by purpose. topic: workflow, import, gates, parallel, memory, recovery, config. Read-only; the pages are templates a project may override.

Input Schema

NameRequiredDescriptionDefault
topicNoworkflow | import | gates | parallel | memory | recovery | config. Omit for the overview, which lists them.
as_agentNoSubagent name, this call only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  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. Changed1 schema field 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"
+}
  4. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and explicitly states the tool is read-only and that returned pages are templates a project may override. It does not describe rate limits or auth needs, but those are unlikely for a local help overview.

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?

Front-loads the purpose and the call-first guidance, then gives topic options. It is dense but mostly earns its length; the phrase 'No argument:' is slightly ambiguous given the optional parameters.

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?

Complete for a read-only help tool with no output schema: it says what the pages cover, including the workflow loop, exit codes, and capabilities grouped by purpose, and notes that projects may override them.

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 coverage is 100%, so the schema already documents both parameters. The description reinforces the topic categories and the overview default, but adds little beyond the schema and does not explain the as_agent 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?

States precisely that this is the overview/help entry point: what ddflow is, what it can do, and the workflow. It distinguishes itself from sibling tools by saying individual tool descriptions and connection instructions do not answer how to work in the project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call this first if the agent has not used ddflow before, and explains why other resources are insufficient. It also names the topic alternatives and says to omit topic for the overview.

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