Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by compasify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getIssueRelations

Retrieve all relations for a specific Redmine issue, including related tasks and dependencies.

Instructions

List issue relations

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": {
      "pathParams": "<pathParams>"
    },
    "name": "getIssueRelations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

D1.8/5.0
Behavior1/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'List issue relations' and says nothing about read-only behavior, required permissions, output format, or error handling. This is a complete absence of behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short ('List issue relations'), but this is under-specification rather than effective conciseness. It lacks essential structure or elaboration, making it unhelpful for the agent.

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

Completeness1/5

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

The tool has no annotations, no output schema, and a nested parameter object. The description provides no context about required parameters, output shape, or behavior, making it severely incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention the required pathParams (format, issueId). The agent gets no help understanding the parameters beyond the raw schema, which is insufficient given the nested object structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List issue relations' provides a clear verb and resource, but it doesn't specify the scope (per issue) or distinguish it from the singular sibling getIssueRelation. The plural form implies multiple relations, but the description remains vague without mentioning the required issueId.

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

Usage Guidelines2/5

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

No usage guidance is provided. There is no information about when to use this tool versus getIssueRelation, createIssueRelation, or other relation-related tools. The agent receives no context for tool selection.

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