Skip to main content
Glama
jesusr00

mcp-server-redmine

by jesusr00

redmine_delete_wiki_page

Permanently deletes a Redmine wiki page by project ID and title. Requires admin privileges and cannot be undone.

Instructions

[Alpha] Permanently delete a Redmine wiki page. Requires admin privileges. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
project_idYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the action is permanent and irreversible, and requires admin privileges. This is adequate for a delete operation, though it could mention error conditions or side effects.

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?

The description is three short sentences with no unnecessary words. The purpose is front-loaded in the first sentence, and each subsequent sentence adds important context.

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?

Given no output schema and simple delete semantics, the description provides core information (permanence, admin requirement). However, it lacks details like error handling, existence checks, or what the response looks like, leaving some ambiguity for the agent.

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?

Schema description coverage is 0%, so the description should compensate, but it does not mention parameters at all. The agent must infer that 'project_id' and 'title' identify the page, but no format or constraints are explained.

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 clearly states the action 'Permanently delete' and the resource 'Redmine wiki page', making the tool's purpose explicit. It distinguishes from sibling delete tools by specifying 'wiki page' in both name and description.

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

Usage Guidelines3/5

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

The description mentions the prerequisite 'Requires admin privileges' and the consequence 'cannot be undone', but does not provide guidance on when to use this tool versus alternatives like updating the page.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jesusr00/mcp-server-redmine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server