roadmap-skill

Overview Schema Source Related Servers Discussions Admin

update_project

Modify an existing project's attributes including status, dates, and description. Set verbose to true to get complete project data in response.

Instructions

Update an existing project. Returns summary by default; set verbose=true for full data.

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": {
      "projectId": "<projectId>"
    },
    "name": "update_project"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`status`	No
`verbose`	No
`projectId`	Yes
`startDate`	No
`targetDate`	No
`description`	No
`projectType`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the return behavior (summary by default, verbose=true for full data), which is useful, but it omits critical behavioral details such as whether this is a partial or full update, permissions required, or side effects.

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 two concise sentences with no filler. It front-loads the action and resources, and the second sentence adds meaningful information about return modes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, no annotations, no output schema, and 0% schema coverage), the description is too sparse. It does not explain update semantics, enum meanings, required fields, or error scenarios, leaving the agent with insufficient context for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, requiring the description to compensate. It only explains the verbose parameter's effect; the other seven parameters lack additional semantic context beyond the schema. This is insufficient for a tool with 8 parameters.

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 an existing project,' naming the verb and resource. This distinguishes it from sibling tools like create_project, delete_project, and update_task by explicitly targeting project updates.

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?

Usage is implied by the verb and resource but not explicitly articulated. The description does not mention when to prefer this over update_task or batch updates, nor does it describe exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.