Skip to main content
Glama
Sign In
Saga MCP

Saga MCP

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

tracker_next

Read-onlyIdempotent

Resume work with a recommended next task, its reason, unfinished subtask, alternatives, and blocker to unblock when nothing is actionable.

Instructions

What to work on next: one recommended task with the reason, its next unfinished subtask, alternatives, and — when nothing is actionable — what to unblock. Call it when resuming work; cheaper than tracker_dashboard.

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

Input Schema

NameRequiredDescriptionDefault
branchNoGit branch filter: "current" = active branch, omit = all.
project_idNoScope to one project. Defaults to SAGA_PROJECT if set, else the whole database.
assigned_toNoOnly consider tasks assigned to this person

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.0
    • changedInput schema / properties / project_id / description
      Previous value: -"Scope to one project. Needed when a single database holds several projects; defaults to the SAGA_PROJECT env var if set, otherwise the whole database."New value: +"Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database."
  2. Addedv1.14.0

TDQS

A4.3/5.0
Behavior4/5

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

The description adds behavioral context beyond the readOnly/idempotent annotations: it returns exactly one recommendation, includes reasoning and alternatives, and defines an unblock path when nothing is actionable. It also adds a performance/cost signal ('cheaper than tracker_dashboard').

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?

Two sentences deliver purpose, output composition, usage timing, and a comparison to the sibling. The most important information is front-loaded and there is no redundancy.

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

Completeness5/5

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

For a read-only recommendation tool with full parameter schema coverage and safety annotations, the description covers everything an agent needs: output structure, when to call it, and behavior when there is nothing actionable. No output schema exists, but the prose specifies the result shape clearly.

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% and every parameter is already well described in the input schema. The tool description adds no parameter-level detail, but that is acceptable because the schema already carries the burden.

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?

The description clearly states that tracker_next produces one recommended task with a reason, its next unfinished subtask, alternatives, and an unblock suggestion. This distinguishes it from list/search tools like tracker_dashboard and tracker_search because it is specifically a recommendation, not a general index.

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 explicitly says 'Call it when resuming work' and positions it as cheaper than tracker_dashboard, giving the agent a clear condition and alternative. It doesn't exhaustively enumerate when not to use it, but the context is sufficient for routing.

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

Deploy Server

Other Tools