Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

roadmap_update

Update the status, priority, or details of a roadmap item. Use to move items through the lifecycle: planned → in-progress → done (or blocked/cancelled). Also use to add notes/findings while working on an 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": {
      "id": "<id>"
    },
    "name": "roadmap_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesItem ID returned by roadmap_add or roadmap_list
notesNoProgress notes, findings, or blockers (appended to existing notes)
titleNoUpdated title (optional)
statusNoNew status for the item
priorityNoUpdated priority (optional)
descriptionNoUpdated description (optional)
instance_idNoUUID of the cache instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the lifecycle progression and that notes are appended to existing notes, but it does not explain permissions, reversibility, what happens to fields not supplied, or the response behavior.

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?

The description is two focused sentences with the primary action front-loaded. It is efficient and readable, with only minor redundancy in restating usage scenarios that are partly evident from the first sentence.

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?

For a seven-parameter mutation tool with no annotations and no output schema, the description covers the main purpose and lifecycle use well. However, it omits behavioral details such as how unspecified fields are handled, permission requirements, and the instance_id parameter's role, leaving some gaps for safe invocation.

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 schema already documents all seven parameters. The description reinforces the status lifecycle values and notes appending behavior, but it adds little syntax or format detail beyond what the schema provides.

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 states a specific verb (Update) and resource (roadmap item) and names the fields affected: status, priority, and details. It is clearly distinct from generic update tools, though it does not explicitly name sibling tools such as roadmap_add or roadmap_list.

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 clear when-to-use guidance: moving items through the planned → in-progress → done lifecycle, including blocked/cancelled, and adding notes/findings. It does not state when not to use this tool or name alternatives for related operations like creation or listing.

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.