PM Context MCP Server

get_current_sprint_tool

Retrieve active sprint details: issue breakdown, completion percentage, in-progress work, blockers, and days remaining to track progress and identify roadblocks.

Instructions

Get the active sprint: issues breakdown, completion percentage, in-progress work, blockers, and days remaining.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_current_sprint_tool"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It clearly signals a read-only operation via 'Get' and lists the output content, but it does not disclose behavior when no active sprint exists or whether the scope is the current user's team/board. This is adequate but lacks some edge-case detail.

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 one efficiently front-loaded sentence: 'Get the active sprint:' immediately identifies the action and resource, followed by a colon-separated list of deliverables. Every word earns its place with no redundant filler.

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

Completeness4/5

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

Given no parameters, no output schema, and no annotations, the description is mostly complete for a simple sprint overview, clearly listing the returned metrics. It falls slightly short by not specifying the sprint's scope (e.g., current team/project) or the outcome when no active sprint is present, but these are minor omissions for a low-complexity tool.

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?

The input schema has zero properties, so with 0 parameters the baseline is 4. There are no parameters for the description to clarify, and its enumerated outputs are sufficient for a no-argument tool.

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 uses a specific verb ('Get') and resource ('active sprint'), then enumerates the exact data returned (issues breakdown, completion percentage, in-progress work, blockers, days remaining). This clearly distinguishes it from sibling tools like get_blockers_tool (blockers alone) or get_my_issues_tool (personal issues).

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?

The description implies use when an active sprint status overview is needed, but it provides no explicit guidance on when to choose this tool over alternatives (e.g., get_blockers_tool or get_roadmap_tool). There are no 'when not to use' or alternative-name mentions, so usage context is only implicit.

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

Deploy Server