redmine-mcp

Overview Schema Source Related Servers Score Discussions Admin

List Redmine issue statuses

list_issue_statuses

Read-onlyIdempotent

Retrieve all Redmine issue statuses, showing each status's ID, name, closed flag, and description in the server's configured order.

Instructions

Read all Redmine issue statuses from GET /issue_statuses.json for the configured Redmine API user. This endpoint accepts no query, include, or pagination controls. Results preserve Redmine's position order and map the current API fields id, name, is_closed, and description to id, name, isClosed, and description, preserving an explicit null or an omitted description. Redmine accepts ordinary API authentication for this index, but its HTML index is admin-or-API-only and there is no status show route, so the result has no browser links. Redmine may return HTTP 401, 403, or 404 without exposing the upstream response body. This tool never changes Redmine data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`issueStatuses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool read-only and idempotent. The description goes well beyond them by disclosing the field-name mapping to camelCase, null/omitted description handling, lack of browser links, and possible HTTP 401/403/404 responses without an exposed body.

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 dense but every sentence carries unique information: endpoint, scope, lack of controls, field mapping, auth/browser-link caveats, error behavior, and non-mutating guarantee. Nothing is wasted or redundant with the annotations.

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?

For a zero-parameter read tool, the description covers endpoint, auth expectations, response mapping, error behavior, and safety. An output schema exists for return values, so the description is fully sufficient for correct invocation.

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?

There are zero parameters, and the schema already reflects this. The description adds meaningful value by explicitly stating that the endpoint accepts no query, include, or pagination controls, removing any doubt about hidden options.

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, resource, and endpoint: 'Read all Redmine issue statuses from GET /issue_statuses.json.' The scope ('all') and resource are unambiguous, and the resource is distinct from every sibling tool.

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

Usage Guidelines4/5

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

Provides clear context: this is a complete read with no query/include/pagination controls and uses ordinary authentication. It does not name alternative tools, but no sibling covers issue statuses, so the omission is acceptable.

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