Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by GonzaloRando03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_journal

Update the notes of an issue journal entry (comment). Requires author or admin access.

Instructions

Updates the notes of an issue journal entry (comment). Requires the user to be the author or an admin.

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": {
      "id": "<id>",
      "notes": "<notes>"
    },
    "name": "update_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric journal ID
notesYesNew text for the journal note

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses permission requirement, but lacks details on side effects, error handling, or reversibility. Adequate but not thorough.

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?

Single sentence, no wasted words. Front-loaded with purpose and condition. Could be slightly more structured but effective.

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?

Tool has 2 parameters, no output schema, no annotations. Description covers purpose and permission but misses potential error cases or response format. Adequate for the complexity.

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 100%, so schema already documents both parameters. Description does not add parameter-specific info beyond the schema. Baseline 3 applies.

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?

Description clearly states 'Updates the notes of an issue journal entry (comment)' – specific verb and resource. Among many update_* tools, this uniquely identifies journal entry updates.

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

Usage Guidelines4/5

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

Includes a clear condition: 'Requires the user to be the author or an admin.' This tells the agent when the tool is permissible. No explicit alternatives or when-not-to-use, but the condition is valuable.

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