Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

roadmap_list

List all roadmap items, optionally filtered by status, priority, tag, or milestone. Returns items sorted by priority then creation date. Called automatically by session_start to show open work.

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

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by tag (optional)
statusNoFilter by status. Use 'open' to see planned+in-progress+blocked (default: open)
priorityNoFilter by minimum priority (optional)
milestoneNoFilter by milestone (optional)
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It adds one genuinely useful trait, the ordering (priority then creation date), but says nothing about result size, truncation, pagination, or whether the read is scoped to the current instance/project — meaningful gaps for a list tool with zero annotation coverage.

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?

Three short sentences, front-loaded with purpose, then return shape, then invocation context. Nothing is padded, though the session_start sentence is tangential to a caller deciding whether to invoke the tool.

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?

There is no output schema and no annotations, so the description should carry more weight than it does; it says results are sorted but never sketches the item shape or volume. For a five-parameter list tool this is adequate but leaves the agent guessing about return payload and scoping.

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 the baseline is 3. The description restates the filter dimensions (status, priority, tag, milestone) already documented in the schema, and notably omits any mention of instance_id or how tag/milestone matching behaves, adding no semantics beyond the schema.

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 uses a specific verb and resource ("List all roadmap items") and names the supported filters, which distinguishes it from the mutating siblings roadmap_add/roadmap_update. It stops short of explicitly contrasting with roadmap_next, which also surfaces roadmap items, so sibling differentiation is implied rather than stated.

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?

It states that filtering is optional and notes it is invoked automatically by session_start for open work, which implies the browse-everything use case. However, there is no explicit guidance on when an agent should call this directly versus roadmap_next for the next actionable item, and no exclusions.

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.