Skip to main content
Glama

Next Task

next_task

Retrieves the highest-priority task that is ready to work on, so you can act only when dependencies are met and the current phase allows it.

Instructions

Get the highest-priority task that is ready to work on (dependencies met, current phase).

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/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 burden. It usefully discloses the selection logic (dependency satisfaction and current-phase filtering), but omits what happens when no task qualifies, how ties are broken beyond 'priority', and whether the task is reserved or mutated in any way.

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?

A single sentence with the key qualifier front-loaded and no filler; the parenthetical compression of the filter conditions is efficient.

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 exists, so return values need not be described, and the single parameter is documented in the schema. What is missing is the empty-result behavior and any note on ordering among equally prioritized tasks, which matters for an agent deciding whether to call this at all.

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 one optional parameter whose schema description ('Project root directory') is fully covered, so the schema already does the work. The description adds nothing about how the path affects which project's tasks are searched, which is the baseline-3 outcome for high coverage.

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 gives a specific verb ('Get') and a precisely scoped resource ('the highest-priority task that is ready to work on'), plus parenthetical selection criteria (dependencies met, current phase). It is clearly distinct from list_tasks and blocked_tasks, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer it should call this when it wants to know what to work on next. There is no explicit guidance on when to prefer this over next_best_action, list_tasks, or blocked_tasks, and no stated exclusions or prerequisites.

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