Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by GonzaloRando03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_issue_agile_data

Retrieve agile fields like sprint, story points, and position for a Redmine issue using the RedmineUP Agile plugin.

Instructions

Gets the agile fields (sprint, story points, position) of an issue. Requires the RedmineUP Agile plugin.

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": {
      "issue_id": "<issue_id>"
    },
    "name": "get_issue_agile_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesNumeric issue ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions the plugin requirement but does not explicitly state read-only status, authentication needs, or behavior when plugin is missing. 'Gets' implies read but is not explicit.

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?

The description is concise with two front-loaded sentences, each adding value: the first states what the tool does, the second states a prerequisite. No unnecessary words.

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

Completeness2/5

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

With no output schema, the description should explain the return format. It lists the fields but not structure, pagination, or error scenarios. Incomplete for a tool with a single parameter and no output schema.

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?

With 100% schema description coverage, the parameter 'issue_id' is already described. The tool description adds no extra meaning beyond the schema, resulting in a baseline score of 3.

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 clearly states the tool gets agile fields (sprint, story points, position) of an issue, specifying the resource and specific fields. It distinguishes from sibling get_issue by focusing on agile data.

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 mentions the required plugin but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like get_issue. Usage is implied but not structured.

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