Redmine MCP Server

redmine_get_project_versions

Get a list of versions/milestones for a Redmine project by providing its project ID or identifier.

Instructions

Get versions/milestones for a specific project

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "redmine_get_project_versions"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID or identifier

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the basic operation without disclosing return format, pagination, or whether archived/inactive versions are included. The 'versions/milestones' synonym adds slight clarity but no substantive behavioral 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 a single, front-loaded sentence that directly states the function with no wasted words. It is appropriately concise for a simple read operation.

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?

The tool is simple (one parameter, no output schema, no annotations). The description adequately states what it retrieves and its scope. It could explicitly say 'returns all versions', but the plural 'versions' implies a list, which is sufficient for a minimal viable description.

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% (project_id described as 'Project ID or identifier'). The description says 'for a specific project', which adds no meaning beyond the parameter name and schema. Baseline 3 applies because the schema fully documents the parameter.

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 'Get versions/milestones for a specific project' uses a specific verb (Get), names the resource (versions/milestones), and scopes it to a project. This clearly distinguishes it from sibling tools like redmine_get_project and no other tool targets versions.

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 usage when a project's versions/milestones are needed but provides no explicit when-to-use, when-not-to-use, or alternative mentions. Since no sibling tool overlaps this functionality, context is implicit rather than explicit.

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