OpenProject CE MCP Server

Overview Schema Source Related Servers Discussions Admin

Get sprint

get_sprint

Read-onlyIdempotent

Retrieves full details for one sprint by ID, including dates, workspace, lifecycle status, and created/updated timestamps after list_sprints supplies the ID.

Instructions

Read one sprint in full: dates, workspace and lifecycle status.

Use it once list_sprints has given you an id and the row is not enough — this adds created_at/updated_at to the same shape.

Pitfalls: sprint ids and version ids are different id spaces — a version id from list_versions does not resolve here.

Cross-references: list_sprints for the id; list_work_packages with sprint_ids for the work planned in this sprint.

Input Schema

Name	Required	Description	Default
`sprint_id`	Yes	Numeric sprint id from list_sprints.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`status`	No
`workspace`	No
`created_at`	No
`start_date`	No
`updated_at`	No
`description`	No
`finish_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed36 schema fields changedv0.4.0Oct 24, 2026

removedOutput schema / description

Removed value: -"A single sprint as ``get_sprint`` returns it."

removedOutput schema / properties / created_at / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / created_at / default
```
Removed value: -null
```
removedOutput schema / properties / created_at / description
```
Removed value: -"ISO 8601 UTC timestamp."
```
addedOutput schema / properties / created_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / description / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / description / default
```
Removed value: -null
```

removedOutput schema / properties / description / description

Removed value: -"Description as markdown (raw); html is dropped."

addedOutput schema / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / finish_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / finish_date / default
```
Removed value: -null
```

removedOutput schema / properties / finish_date / description

Removed value: -"ISO date (YYYY-MM-DD); the sprint's finish date (wire 'finishDate')."

addedOutput schema / properties / finish_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / id / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / id / default
```
Removed value: -null
```

removedOutput schema / properties / id / description

Removed value: -"Sprint id — what the work-package 'sprint' field consumes."

addedOutput schema / properties / id / type

Added value: +[
+  "integer",
+  "string",
+  "null"
+]

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / name / default
```
Removed value: -null
```
removedOutput schema / properties / name / description
```
Removed value: -"Sprint name, e.g. 'Sprint 11'."
```
addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / start_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / start_date / default
```
Removed value: -null
```
removedOutput schema / properties / start_date / description
```
Removed value: -"ISO date (YYYY-MM-DD)."
```
addedOutput schema / properties / start_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / status / default
```
Removed value: -null
```

removedOutput schema / properties / status / description

Removed value: -"in_planning, active or completed (parsed from the status URN)."

addedOutput schema / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / updated_at / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / updated_at / default
```
Removed value: -null
```
removedOutput schema / properties / updated_at / description
```
Removed value: -"ISO 8601 UTC timestamp."
```
addedOutput schema / properties / updated_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / workspace / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "A reference to another resource. Canonical output shape.",
-    "properties": {
-      "id": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Resource id."
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Human-readable name."
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": [
+          "integer",
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / workspace / default
```
Removed value: -null
```

removedOutput schema / properties / workspace / description

Removed value: -"The project (workspace) that DEFINES the sprint."

Addedv0.3.3Oct 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: the response is the list shape plus created_at/updated_at, and sprint ids live in a different id space than version ids. It stops short of saying what happens on a bad or foreign id, but the added behavioral detail is meaningful.

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?

Front-loaded with purpose, then usage, pitfalls, and cross-references in clearly labeled chunks. Every sentence carries information; nothing is redundant.

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

Completeness5/5

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

An output schema exists so return values need not be explained, and the description still covers when to call it, what it adds over the list endpoint, the id-space hazard, and follow-on tools. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by warning that a version id from list_versions will not resolve here, which is semantic guidance the schema's 'Numeric sprint id from list_sprints' only hints at.

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?

States a specific verb and resource ('Read one sprint in full') plus the returned facets (dates, workspace, lifecycle status), which lets an agent separate it from list_sprints without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says to use it only after list_sprints has supplied an id and the list row is insufficient, and names cross-references (list_sprints for the id, list_work_packages with sprint_ids for contents). Both the when and the boundaries are stated.

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

Deploy Server