Skip to main content
Glama
robertsmieja

xmatters-mcp

by robertsmieja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete a group

xmatters_delete_a_group
Destructive

Delete a group from xMatters by its ID. Requires explicit confirmation and operator write access to permanently remove the group.

Instructions

Delete a group. DELETE /api/xm/1/groups/{groupID}. Body fields: none. Reference: https://help.xmatters.com/xmapi/#delete-a-group Requires operator write opt-in and confirm:true; may notify recipients or change tenant data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
queryNoAPI query parameters; arrays are comma-joined. Documented names: none. Pagination is explicit using offset and limit; results are not automatically combined.
confirmYesExplicit approval of this exact mutation. Operator must also enable XMATTERS_ALLOW_WRITES.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds behavioral context beyond annotations: 'may notify recipients or change tenant data' and requires confirm:true. Annotations already flag destructiveHint=true, but the description elaborates on side effects and prerequisites.

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?

Concise single sentence with endpoint and reference link. However, it repeats 'Delete a group' from the title, and the reference link may be redundant. Still, it is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides essential info: endpoint, requirements, and side effects. Lacks description of groupID meaning, but context from resource name implies it. Adequate for a delete tool.

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 covers confirm and query with descriptions, but the description does not clarify the groupID parameter beyond its presence in the path. 'Body fields: none' is unrelated to parameters, so no additional meaning is provided.

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?

States the exact operation ('Delete a group') and specifies the HTTP endpoint (DELETE /api/xm/1/groups/{groupID}). This clearly distinguishes it from sibling tools like get, create, or modify group operations.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention sibling tools or conditions under which deletion is appropriate. It only lists prerequisites (operator write opt-in and confirm:true), which are requirements rather than usage guidelines.

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