Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by compasify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search

Query Redmine content across issues, projects, wiki pages, documents, messages, changesets, and attachments, applying filters like scope, open issues, and all words to refine results.

Instructions

Search

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>",
      "queryParams": "<queryParams>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathParamsYes
queryParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

D1.1/5.0
Behavior1/5

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

No annotations are provided, and the description reveals nothing about potential side effects, authentication requirements, rate limits, or the nature of results. The one-word description carries no behavioral information.

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, but this is under-specification rather than conciseness. A single word does not earn its place as it provides no utility to 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?

Given the tool has a complex nested schema with many search options and no output schema, a one-word description is completely inadequate. The agent cannot determine correct usage or expected results.

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?

The schema has 0% description coverage, and the description adds no meaning to parameters. Many parameters exist (limit, offset, scope, q), but their purpose, constraints, and interactions are entirely unexplained.

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

Purpose1/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, what scenarios it is suited for, or any alternatives. The description is entirely absent of usage context.

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