Skip to main content
Glama
Sign In
Cachly — AI Cognitive Brain

Cachly — AI Cognitive Brain

by cachly-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

roadmap_update

Update the status, priority, or details of a roadmap item to move it through its lifecycle or log progress notes and blockers.

Instructions

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": {
      "instance_id": "<instance_id>",
      "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_idYesUUID of the cache instance

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so full burden on description. It discloses that notes are appended, but does not mention persistence, authorization, or error conditions (e.g., invalid item ID). Adequate but not thorough.

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, front-loaded with verb and resource, every sentence earns its place. No redundancy or fluff.

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?

Covers main actions and lifecycle, but with 7 parameters and no output schema, it omits details on optional parameter behavior (e.g., partial updates) and potential errors. Adequate for typical usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds value by explaining the lifecycle context for the status parameter. Other parameters are well-described in schema; description does not add much beyond.

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 'Update the status, priority, or details of a roadmap item' and specifies the lifecycle transitions (planned → in-progress → done/blocked/cancelled). It effectively distinguishes from siblings like roadmap_add and 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?

Provides clear usage context: moving items through lifecycle and adding notes. However, lacks explicit when-not-to-use or comparison with alternative tools (e.g., roadmap_next).

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