Skip to main content
Glama

roadmap_add

Propose a manager-only roadmap outcome with title, desired result, priority, dependencies, acceptance criteria, and evidence; does not create or launch a task.

Instructions

Manager-only Roadmap proposal; does not create or launch a task.

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

Input Schema

NameRequiredDescriptionDefault
titleYesShort outcome title; required, at most 1000 bytes.
outcomeYesWhat the roadmap item should achieve; required, at most 100000 bytes.
priorityNocritical, high, medium or low; default medium.medium
milestoneNoFree-text milestone label, truncated to 500 characters; default empty.
acceptanceNoAcceptance criteria, up to 100 non-blank strings; completing the outcome later requires at least one.
depends_onNoRoadmap ids (RM-YYYY-NNNNN) that must exist and be completed before this outcome can be approved, started or completed.
provenanceNoFree-form JSON object recording where the proposal came from; the server adds origin and verified=true.
needfix_idsNoNeedFix ids (NF-YYYY-NNNNN) behind this outcome; each NeedFix must already be accepted, task_planned, task_created or resolved.
evidence_refsNoEvidence reference strings, up to 200; completing an outcome that has no linked task needs at least one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.12.67
    • addedInput schema / properties / acceptance / description
      Added value: +"Acceptance criteria, up to 100 non-blank strings; completing the outcome later requires at least one."
    • addedInput schema / properties / depends_on / description
      Added value: +"Roadmap ids (RM-YYYY-NNNNN) that must exist and be completed before this outcome can be approved, started or completed."
    • addedInput schema / properties / evidence_refs / description
      Added value: +"Evidence reference strings, up to 200; completing an outcome that has no linked task needs at least one."
    • addedInput schema / properties / milestone / description
      Added value: +"Free-text milestone label, truncated to 500 characters; default empty."
    • addedInput schema / properties / needfix_ids / description
      Added value: +"NeedFix ids (NF-YYYY-NNNNN) behind this outcome; each NeedFix must already be accepted, task_planned, task_created or resolved."
    • addedInput schema / properties / outcome / description
      Added value: +"What the roadmap item should achieve; required, at most 100000 bytes."
    • addedInput schema / properties / priority / description
      Added value: +"critical, high, medium or low; default medium."
    • addedInput schema / properties / provenance / description
      Added value: +"Free-form JSON object recording where the proposal came from; the server adds origin and verified=true."
    • addedInput schema / properties / title / description
      Added value: +"Short outcome title; required, at most 1000 bytes."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world operation. The description adds meaningful context beyond annotations: the operation is manager-restricted and does not create or launch tasks, which is important for an add/mutation tool.

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?

The description is extremely short, front-loads the manager-only restriction, and contains no filler. Both clauses carry useful information for tool selection.

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?

The schema richly documents the nine parameters and annotations cover safety traits, but the description is very terse for a mutation tool and does not explain what is returned or what lifecycle state the proposal enters. It is minimally adequate but leaves meaningful contextual gaps.

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 nine parameters are already well documented in the schema. The description adds no parameter-specific semantics, which is acceptable at the baseline level but does not exceed it.

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 identifies the resource as a Roadmap proposal and adds the manager-only restriction, while explicitly distinguishing it from task creation/launching. It is clear enough to separate it from task tools, though it does not use an explicit verb like 'adds' or distinguish among the roadmap_* siblings.

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 gives a useful actor restriction ('Manager-only') and an explicit when-not boundary ('does not create or launch a task'). However, it does not name alternatives such as roadmap_show, roadmap_transition, or roadmap_link_task, so the agent must infer when to choose this over other roadmap operations.

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