Skip to main content
Glama

Coline

Find the next task to take

next_task
Read-onlyIdempotent

For an agent working for its person: the tasks it may take, best first. Tasks marked for this agent and work sent back to it come first, then tasks given to its person; never blocked, done or held by another agent; highest priority, then soonest due. Take one with take_task before working on it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "next_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower, yet the description still adds real behavioral detail: eligibility excludes blocked, done, and tasks held by another agent, and results are ordered by assignment to this agent/work returned, then given to its person, then priority, then due date. It stops short of stating that an empty result is possible or how truncation interacts with the ranking.

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?

It is front-loaded with the audience qualifier, then eligibility, then ordering, then the follow-up action, with essentially no filler. The single long clause listing ordering keys is dense but still readable.

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?

The output schema exists, so return shape needn't be explained, and the tool is a simple two-parameter read. The remaining gap is the undocumented limit parameter's effect, which is minor but real.

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 50%: workspace is documented in the schema while limit is not described anywhere, and the description never says results are capped at limit or that limit defaults to 5 and maxes at 20. The ranking language makes the concept of a top-N list clearer, but this is baseline-level compensation for the coverage 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 names a specific resource (tasks the agent may take) and a specific ordering contract ('best first'), so an agent knows this is a ranked eligibility listing rather than a search or a mutation. It does not explicitly contrast with the near-name sibling find_task, which a 5 would require.

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

Usage Guidelines4/5

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

It scopes the audience ('For an agent working for its person') and prescribes the next step: 'Take one with take_task before working on it.' That is clear context for when to call it, but there are no explicit when-not conditions or named alternatives for ad-hoc lookup versus next-available.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources