Skip to main content
Glama
vish288

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Confluence Sprint Capacity

confluence_sprint_capacity
Read-onlyIdempotent

Calculate sprint capacity by accounting for team time-off and working days per week, so you can plan realistic sprint workloads.

Instructions

Calculate sprint capacity considering team time-off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprint_endYesSprint end date: YYYY-MM-DD, 'today', 'tomorrow', '+Nd', '-Nd', 'next week'
sprint_startYesSprint start date: YYYY-MM-DD, 'today', 'tomorrow', '+Nd', '-Nd', 'next week'
team_membersYesFull names exactly as they appear on the calendar
working_days_per_weekNoWorking days per week

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed3 schema fields changedv0.10.1
    • changedInput schema / properties / sprint_end / description
      Previous value: -"Sprint end date"New value: +"Sprint end date: YYYY-MM-DD, 'today', 'tomorrow', '+Nd', '-Nd', 'next week'"
    • changedInput schema / properties / sprint_start / description
      Previous value: -"Sprint start date"New value: +"Sprint start date: YYYY-MM-DD, 'today', 'tomorrow', '+Nd', '-Nd', 'next week'"
    • changedInput schema / properties / team_members / description
      Previous value: -"List of team member names"New value: +"Full names exactly as they appear on the calendar"
  3. First observedv0.6.13

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, lowering the bar. The description adds one genuine behavioral detail not in the schema: time-off is factored in automatically (there is no time-off parameter). It still says nothing about how capacity is derived or what the result contains.

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?

A single front-loaded sentence with zero padding. It is efficient, though its extreme brevity borders on under-specification rather than optimal conciseness.

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?

Parameters are fully covered by the schema and safety is covered by annotations, so the tool is callable as-is. However, with no output schema, the description could usefully state what the capacity result looks like, and it omits any guidance on the calendar/time-off dependency, so it is only minimally complete.

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 four parameters (including date-format options and the working_days_per_week default) are already documented. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 names a specific verb and resource ('Calculate sprint capacity'), so the agent knows exactly what computation this performs. It does not, however, differentiate itself from related siblings like confluence_list_calendars and confluence_get_time_off, which supply the underlying data.

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?

There is no when-to-use guidance, no mention of alternatives, and no statement of prerequisites (e.g., that calendar/time-off data must be accessible). The agent must infer usage entirely from the name and schema.

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