Skip to main content
Glama
mcp-server-redmine

mcp-server-redmine

by jesusr00

redmine_update_wiki_page

Create or update a Redmine wiki page, automatically creating it if missing. Pass the current version to prevent overwriting concurrent edits.

Instructions

[Alpha] Create or update a Redmine wiki page. If the page does not exist, it will be created. IMPORTANT: Always fetch the page first with redmine_get_wiki_page and pass the current 'version' number to avoid silently overwriting concurrent edits.

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>",
      "title": "<title>",
      "text": "<text>"
    },
    "name": "redmine_update_wiki_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
titleYes
versionNo
commentsNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.8.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / project_id / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[a-zA-Z0-9_-]+$",
      -    "type": "string"
      -  },
      -  {
      -    "exclusiveMinimum": 0,
      -    "type": "integer"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[a-zA-Z0-9_-]+$",
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  }
      +]
    • addedInput schema / properties / version / maximum
      Added value: +9007199254740991
  2. First observedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral traits: upsert behavior and the silent-overwrite risk mitigated by version. It omits permission requirements and what the response contains, but the destructive-risk disclosure is the most important part and is present.

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?

Three short sentences, front-loaded with the action, then the upsert condition, then the critical warning. No wasted wording; the '[Alpha]' tag is the only extraneous element.

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

Completeness3/5

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

For a 5-parameter mutation tool with no annotations and no output schema, the description covers the upsert and concurrency story but leaves the remaining parameters and the return behavior unexplained, so it is only partially complete.

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 0% across 5 parameters, so the description must compensate. It explains the purpose of 'version' well (concurrency control) but says nothing about 'text', 'comments', or 'project_id' formats or constraints, leaving most parameters undocumented.

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?

States a specific verb and resource ('Create or update a Redmine wiki page') and clarifies the upsert semantics, which cleanly separates it from the get/delete/list wiki siblings.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite workflow: fetch first with redmine_get_wiki_page and pass the current 'version'. It also states the create-if-missing condition, so the agent knows exactly when and how to call it.

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