Skip to main content
Glama

List Unblocked Task DAG Wavefront

nomos_task_dag
Read-onlyIdempotent

Queries unblocked causal DAG wavefront tasks with scope paths and TC-* obligations to select the next INT-* or SUB-* task for execution without mutating ledger state.

Instructions

Query unblocked causal DAG wavefront tasks (including Agent-to-Agent scope_paths, TC-* obligations, and active worktree MTPO overlap flags) ready for execution without mutating task ledger state. Use when selecting the next unblocked INT-* or SUB-* task to start (to submit a new multi-node DAG subgraph, invoke CLI 'nomos task batch -F - --json'). Do NOT use when recalling past architectural decisions or lessons (use nomos_mem_recall instead).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nomos_task_dag"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoTarget repository root or subdirectory path (defaults to current working directory)..
limitNoMaximum number of unblocked wavefront tasks to return.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of returned records.
itemsYesUnblocked wavefront task candidates with scope_paths, obligations, and overlaps_active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'without mutating task ledger state' largely restates structured data rather than adding to it. It does clarify which state is untouched (the task ledger), but omits ordering/priority semantics of the 'wavefront' and any note about how limit truncates results.

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?

Three sentences, front-loaded with the scope, then when-to-use, then when-not-to-use; nothing is filler. It is dense and jargon-heavy, which costs a little readability, but every clause carries routing information.

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 return values need no explanation, and the description covers purpose, safe-read behavior, and sibling routing for a two-parameter read tool. The only gap is that it does not explain what determines the ordering of unblocked tasks or how limit interacts with the wavefront.

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%, with both 'dir' and 'limit' fully documented including defaults, bounds and examples. The description adds no meaning beyond that, so the baseline of 3 applies.

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: 'Query unblocked causal DAG wavefront tasks' with concrete scope (scope_paths, TC-* obligations, MTPO overlap flags) and the key constraint that it does not mutate ledger state. The contrast with nomos_mem_recall makes the boundary unambiguous despite heavy domain jargon.

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 when to use it ('selecting the next unblocked INT-* or SUB-* task to start'), names the sibling to use instead for a different intent ('nomos task batch -F - --json' for submitting a new subgraph), and gives an explicit when-NOT-to-use routing to nomos_mem_recall. All three cases are stated, not inferred.

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