Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

roadmap_next

Get the single most important next actionable roadmap item. Returns the highest-priority in-progress item first, then planned items, sorted by priority. Call at session start to immediately know what to work on next.

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

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by tag (optional)
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the non-obvious behavior: exactly one item is returned and the ranking is in-progress items first, then planned, by priority. Gaps remain on edge behavior, such as what is returned when no items exist or whether the tag parameter narrows the candidate set before ranking.

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?

Three short sentences, front-loaded with the core action, then the ranking rule, then the usage trigger. Every sentence adds distinct information and none repeats the name or schema.

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?

For a two-optional-parameter read tool with no output schema, the description covers the essentials: cardinality, ordering logic, and when to call it. It could still be richer by indicating what fields a returned item contains, since there is no output schema to fall back on.

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%, so both tag and instance_id are already documented in the schema. The description adds nothing about the parameters and notably never mentions that tag filtering interacts with which item is selected as 'most important'. Baseline 3 applies since the schema does the work.

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 states a specific verb and resource ('Get the single most important next actionable roadmap item') plus a scope constraint ('single') that separates it from list-style siblings like roadmap_list. The selection rule ('highest-priority in-progress item first, then planned') further pins down what this tool returns versus a general roadmap query.

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 gives an explicit trigger: 'Call at session start to immediately know what to work on next.' That is clear when-to-use guidance with a concrete moment in the workflow. It stops short of naming when-not to use it or pointing to alternatives such as roadmap_list for browsing the full backlog.

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.