delete_group
Permanently remove a group from Redmine by specifying its numeric ID.
Instructions
Deletes a group permanently.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric group ID to delete |
Permanently remove a group from Redmine by specifying its numeric ID.
Deletes a group permanently.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric group ID to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only states 'permanently' to indicate irreversibility, but does not disclose effects on group members, associated data, or required authorization, leaving important behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise and front-loaded, but could be slightly expanded for completeness without losing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description lacks context about side effects (e.g., user membership, cascade deletion) and return behavior. Adequate for the simple parameter set but incomplete for safe agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with a clear description for 'id'. The tool description adds no additional meaning beyond the schema, so baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description specifies 'Deletes a group permanently' using a clear verb and resource, distinguishing it from sibling tools like create_group and update_group.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, such as checking if the group is in use or if deletion requires certain permissions. No explicit context for agent decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GonzaloRando03/redmine-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server