Skip to main content
Glama

Blocked Tasks

blocked_tasks

Lists all tasks blocked by dependencies or explicitly flagged, helping you identify and resolve project workflow bottlenecks.

Instructions

List all tasks that are blocked, either by dependencies or explicitly.

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": "blocked_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully defines what 'blocked' means (dependencies or explicit marking), but says nothing about whether it scans the whole project, whether results are ordered or paginated, or what state the calling agent needs.

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?

One short sentence with the key qualifier ('blocked') front-loaded and zero filler. It is efficient, though its brevity leaves useful routing context on the table.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema is declared, so return values need not be explained, and the tool is simple with one optional parameter. Still, given roughly eighty siblings including several task-listing tools, the description should say how this differs from list_tasks.

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?

There is a single optional parameter with 100% schema description coverage ('Project root directory'), so the schema already documents it. The description adds no further meaning about path scoping, which is the baseline-3 case.

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 names a specific verb and resource ('List all tasks that are blocked') and even clarifies the two blocking modes (dependency-based vs. explicit). It does not, however, distinguish the tool from the closely named sibling list_tasks, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as list_tasks or next_task. The agent must guess that this is the filtered subset of task listing rather than a general task query.

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