Retrieve all available work package statuses from OpenProject to identify valid statuses for filtering and reporting. Read-only: statuses are configured in the admin UI.
List all available work package statuses.
Read-only: statuses cannot be created or modified via the OpenProject API (Community Edition); configure them in the web admin UI.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.3.7Input schema / additionalPropertiesAdded value: +falsev0.2.3Output schema / (root)Previous value: -{
- "$defs": {
- "StatusSummary": {
- "properties": {
- "color": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Color"
- },
- "id": {
- "title": "Id",
- "type": "integer"
- },
- "is_closed": {
- "title": "Is Closed",
- "type": "boolean"
- },
- "is_default": {
- "title": "Is Default",
- "type": "boolean"
- },
- "name": {
- "title": "Name",
- "type": "string"
- },
- "position": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "title": "Position"
- },
- "url": {
- "title": "Url",
- "type": "string"
- }
- },
- "required": [
- "id",
- "name",
- "is_default",
- "is_closed",
- "color",
- "position",
- "url"
- ],
- "title": "StatusSummary",
- "type": "object"
- }
- },
- "properties": {
- "count": {
- "title": "Count",
- "type": "integer"
- },
- "results": {
- "items": {
- "$ref": "#/$defs/StatusSummary"
- },
- "title": "Results",
- "type": "array"
- }
- },
- "required": [
- "count",
- "results"
- ],
- "title": "StatusListResult",
- "type": "object"
-}New value: +nullv0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly states that the operation is read-only and that statuses cannot be created or modified via the API, providing clear behavioral expectations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief and to the point, conveying all necessary information without extraneous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description fully covers what the tool does, its read-only nature, and where to manage statuses, making it complete for an agent to decide and use the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so the description does not need to elaborate on parameter meanings. The absence of parameters is consistent with the description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool lists all available work package statuses, which is a specific and distinct action. It differentiates from sibling tools by focusing on statuses.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies when to use the tool (when needing to retrieve statuses) and explicitly notes that statuses cannot be modified via API, directing configuration to the web admin UI. It does not explicitly mention alternatives, but the scope is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jtauschl/openproject-ce-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server