Project Tracker MCP Server

by spranab

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

update_story

Modify a story's details like title, status, priority, or hours to keep project tracking accurate.

Instructions

Update story information

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": {
      "story_id": "<story_id>"
    },
    "name": "update_story"
  }
}

Input Schema

Name	Required	Description
`title`	No	New title for the story
`status`	No	New status for the story
`priority`	No	New priority for the story
`story_id`	Yes	UUID of the story to update
`description`	No	New description for the story
`actual_hours`	No	New actual hours for the story
`estimated_hours`	No	New estimated hours for the story

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. The word "Update" implies a state-changing operation, but the description does not disclose partial-update semantics, required permissions, side effects, idempotency, or failure behavior. This leaves major behavioral gaps for a 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only four words, which is extremely terse and under-specified for a tool with seven parameters. While it is front-loaded and free of filler, it provides too little information to be useful to an agent.

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?

For a complex mutation tool with no annotations and no output schema, the description omits key context such as update semantics, return values, and error behavior. Although the schema fully documents parameters, the lack of behavioral detail leaves the definition contextually incomplete.

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, including the required story_id and the two enum fields. The description adds no additional parameter meaning or syntax beyond what the schema provides, making the baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a generic verb and resource ("Update story information"), making the basic action clear. However, it does not specify what story information can be updated or distinguish this tool from sibling update tools like update_issue or update_epic. It is minimally viable but vague about scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as create_story, delete_story, or get_story. There is also no mention of prerequisites or whether it performs a partial or full update. The agent must infer all usage conditions.

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