Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by onozaty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getWikiPages

Read-only

Retrieve a list of wiki pages for a specified Redmine project. Get an overview of available wiki content in JSON or XML format.

Instructions

List wiki pages

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": "getWikiPages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description does not contradict it. However, the description adds no behavioral context beyond the annotation, such as scope, return shape, or pagination behavior, so it provides only minimal value.

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 a single, direct sentence with no filler, and the action verb is front-loaded. It is concise, though the brevity partly reflects under-specification rather than deliberately compact completeness.

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 a required nested parameter object and no output schema, the description is too thin: it does not state that projectId is required, that format can be json or xml, or what the list operation returns. The schema provides parameter mechanics, but the agent gets no broader context about scope or output.

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 says nothing about pathParams, projectId, or format. The agent must rely entirely on the raw schema for parameter semantics, which is a significant gap for a required nested parameter object.

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 uses the specific verb 'List' and identifies the resource 'wiki pages', making the basic operation clear. The plural 'pages' distinguishes it from singular sibling tools like getWikiPage and getWikiPageByVersion, even though project scope is not mentioned.

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?

There is no guidance on when to use this tool instead of getWikiPage, getWikiPageByVersion, or other list-style tools. The description does not mention that projectId is required or that format should be chosen, leaving usage decisions entirely to inference.

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