Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

roadmap_add

Add a new item to the persistent project roadmap stored in the Brain. Items survive across sessions and editors — the roadmap is always up to date. Use for features, bugs, refactors, or any planned work. Call roadmap_list to see all open items, roadmap_next to get the next actionable item.

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": {
      "title": "<title>"
    },
    "name": "roadmap_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags for filtering (e.g. ["api", "web", "sdk", "infra"])
titleYesShort title of the task/feature (3–10 words)
priorityNoPriority level (default: medium)
milestoneNoMilestone/epic this belongs to (optional)
descriptionNoWhat needs to be done, acceptance criteria, context
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add one genuinely useful trait: items persist across sessions and editors. But it says nothing about what a write actually does — whether it returns an item ID, whether duplicate titles are merged or rejected, what validation/priority defaults apply on write, or whether the operation is reversible.

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 sentences, front-loaded with the action and destination, then durability, then routing. Every sentence carries distinct information with no repetition of the tool name or schema fields.

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 six-parameter mutation tool with no annotations and no output schema, the description covers purpose, durability, and sibling routing adequately. The remaining gap is the post-call contract: without an output schema, the description should indicate whether a new item identifier or confirmation comes back and how duplicates are treated.

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 all six parameters including the priority enum and instance_id UUID are already documented in the schema; baseline is 3. The description adds no parameter-level meaning beyond the schema — it does not explain, for example, how tags are used for the filtering that roadmap_list presumably performs.

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?

"Add a new item to the persistent project roadmap stored in the Brain" gives a specific verb (add) and resource (project roadmap) plus where it lives. It explicitly separates itself from roadmap_list and roadmap_next, so an agent can route between them without opening any schema.

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?

"Use for features, bugs, refactors, or any planned work" plus pointers to roadmap_list and roadmap_next gives clear positive guidance and names alternatives. It stops short of stating when NOT to use it — e.g. that ephemeral notes belong in remember_context or cache_set rather than the persistent roadmap — so the boundary against non-roadmap siblings is left implicit.

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.