Skip to main content
Glama
Sign In
DutyHub MCP Server

DutyHub MCP Server

by K-ulucay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

complete_sprint

Complete a sprint by setting its status to completed, effectively closing it in the project.

Instructions

Sprinti tamamlar/kapatır (status → completed).

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": {
      "sprint_id": "<sprint_id>"
    },
    "name": "complete_sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
sprint_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

The description discloses that the tool changes sprint status to 'completed', which is a basic behavioral trait. However, with no annotations, it does not cover permissions, reversibility, 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.

Conciseness4/5

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

The description is a single sentence, highly concise. It could benefit from slightly more structure but avoids verbosity.

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 simple action with one parameter, the description is minimally adequate. However, it lacks usage context and parameter details, making it incomplete for an informed tool selection.

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

Parameters1/5

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

The description does not explain the sprint_id parameter beyond its role as identifier. With 0% schema description coverage and no elaboration, the agent gets no added value.

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 the tool completes/closes a sprint and changes its status to 'completed'. This distinguishes it from sibling tools like start_sprint.

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 (e.g., update_task_status), nor any prerequisites like requiring the sprint to be in a certain state.

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