Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by compasify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

deleteNews

Delete a Redmine news entry by its unique ID, with response format choices of JSON or XML.

Instructions

Delete 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>"
    },
    "name": "deleteNews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.4

TDQS

C2.6/5.0
Behavior2/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 explaining the destructive nature of the operation. It only says 'delete', implying mutation but not disclosing irreversibility, permissions, cascading effects, or other behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, but it is under-specified. It lacks structure and does not provide enough information to be considered well-crafted. It is not verbose, but it sacrifices necessary details for brevity.

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?

For a destructive operation with nested parameters and no output schema, the description is insufficient. It fails to mention the required pathParams or provide context about the operation's effects, leaving the agent without essential information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning beyond the schema. It does not explain the purpose of the pathParams, newsId, or format. Since schema coverage is 0%, the description fails to compensate for the lack of parameter explanation.

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

Purpose4/5

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

The description 'Delete news' clearly states the verb and resource, distinguishing it from other delete tools like deleteProject and deleteUser. It is specific enough to identify the action, though it lacks additional scope or context.

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. It does not mention prerequisites, exclusions, or any context that would help an agent decide between deleting a news item and other operations.

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