Skip to main content
Glama
robertsmieja

xmatters-mcp

by robertsmieja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a shift

xmatters_create_a_shift
Destructive

Create a shift for an xMatters group. Use the group ID, shift name, and schedule details to set up on-call coverage, requiring explicit confirmation for the change.

Instructions

Create a shift. POST /api/xm/1/groups/{groupID}/shifts/. The definition omits its initial slash; the standard base URL and request examples establish the full root path. Its trailing slash is preserved. Name is required; start/end and recurrence fields are conditional. See C04. Body fields: name, description, recurrence, members, siteHolidays, timezone, start, end, rotation, repeatEscalation, notifyEndofEscalation, notifyEndOfEscalation. Reference: https://help.xmatters.com/xmapi/#create-a-shift Requires operator write opt-in and confirm:true; may notify recipients or change tenant data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesComplete API JSON payload (including nested fields). See https://help.xmatters.com/xmapi/#create-a-shift
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

A4/5.0
Behavior4/5

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

Adds meaningful side-effect disclosure: 'may notify recipients or change tenant data' and requires operator write opt-in plus confirm:true. These go beyond the raw annotations, which only flag mutating and destructive behavior. No contradiction with annotations.

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?

Though informative, the description mixes endpoint URL details, field lists, cross-references, and prerequisites in a single dense block. The trailing-slash clarification and cryptic 'See C04' add noise; a short structured list would be clearer.

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?

Covers the key operational facts: endpoint, required/conditional fields, authentication opt-in, and side effects. Because there is no output schema, a statement about the response (e.g., the created shift) would improve completeness, but overall it is sufficient for a create mutation.

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

Parameters4/5

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

The schema has high coverage (75%) but only documents name, path, and a generic body object. The description supplements it by listing the full set of acceptable body fields and marking name as required and start/end/recurrence as conditional, enriching the otherwise permissive schema.

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 and resource: 'Create a shift.' It specifies the exact HTTP endpoint, distinguishing it from other shift tools like update/delete/get. The difference from siblings is apparent from the verb and endpoint.

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?

Provides no explicit guidance on when to choose this tool over siblings such as xmatters_update_a_shift_by_id. The required/conditional field notes are parameter-level, not use-case selection. Usage must be inferred from the tool name.

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