Skip to main content
Glama

Next Best Action

next_best_action

Calculates the next task to work on using phase, priority, dependencies, and file hints, so teams can choose work in the right order.

Instructions

Intelligently calculate and recommend the next best task to work on based on phase, priority, dependencies, and file hints.

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_best_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/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 burden. It does disclose the ranking factors (phase, priority, dependencies, file hints), which is genuine behavioral context, but it never states whether the tool only reads/ranks or also mutates task state, nor whether it requires an initialized project context.

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?

A single front-loaded sentence with no redundant clauses. The adverb 'Intelligently' is mild filler, but the sentence otherwise earns its place and is easy to scan.

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?

An output schema exists, so return values need not be explained, and the ranking criteria are stated. Still missing for a tool of this role are the relationship to next_task, the meaning of the path parameter, and whether calling it changes any state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter 'path' (default '.') is never mentioned in the description. The agent gets no explanation of whether path scopes the project root, the workspace, or the file-hint scan, so the description fails to compensate for the schema gap.

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 pair ('calculate and recommend') and a clear resource ('the next best task'), and it names the inputs driving the ranking (phase, priority, dependencies, file hints). It does not, however, distinguish itself from the sibling next_task, which sounds like it does something very similar, so an agent cannot tell the two apart from the text alone.

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 explicit when-to-use guidance, no prerequisites, and no mention of the obvious alternative next_task or of blocked_tasks/list_tasks. The phrase 'task to work on' only weakly implies the usage context, leaving the agent to guess which of the several task-selection siblings to call.

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