Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by compasify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

getNews

Retrieve Redmine news details by ID, optionally including attachments and comments, in JSON or XML format.

Instructions

Show news

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

Input Schema

NameRequiredDescriptionDefault
pathParamsYes
queryParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of conveying behavioral traits. 'Show news' gives no indication of read-only behavior, required permissions, output format, pagination, or error semantics. The tool could be interpreted as a read operation, but this is not explicitly stated.

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 ('Show news'), which is under-specification rather than effective conciseness. It does not provide necessary details about the tool's operation or parameters, so the brevity is not value-adding.

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 a nested object schema with required parameters and no output schema, so the description must compensate for this complexity. 'Show news' is completely inadequate: it fails to explain the news ID requirement, the format option, the include query parameter, or any expected response.

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 adds no meaning to the parameters. The schema defines pathParams with format and newsId, and queryParams with include, but the description does not explain their purpose or acceptable values, leaving the agent with only raw schema structure and no semantic context.

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

Purpose2/5

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

The description 'Show news' merely restates the tool name 'getNews' without specifying the resource scope, action detail, or differentiation from sibling tools like getNewsList and getNewsListByProject. It does not indicate that this tool retrieves a single news item by ID or supports format/include options.

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 versus alternatives. The description does not mention that getNews likely fetches a single news item by ID, nor does it reference getNewsList or getNewsListByProject for broader queries.

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