teamgrid_absence_create

teamgrid_absence_create is a write-capable TeamGrid MCP tool. It is advertised in: full, schedule-write.

Create an absence. Changes the selected workspace under current API permissions. Reuse the same idempotencyKey and payload for the same intent.

Arguments at a glance

The table describes full. When a profile variant is shown below, use that variant’s exact schema.

Input schema

Stable release: this is the exact JSON Schema advertised by @teamgrid/mcp-server@1.2.2:

{
  "type": "object",
  "properties": {
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "description": "Workspace returned by teamgrid_workspace_get and selected for this exact action."
    },
    "idempotencyKey": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "pattern": "^[\\x21-\\x7e]+$",
      "description": "Stable key for this exact intent. Retain and reuse the same key and payload after a timeout; a timeout does not prove failure."
    },
    "data": {
      "additionalProperties": false,
      "properties": {
        "end": {
          "format": "date-time",
          "type": "string",
          "description": "End timestamp of the represented interval."
        },
        "reason": {
          "maxLength": 1000,
          "type": [
            "string",
            "null"
          ],
          "description": "The reason associated with this absence."
        },
        "start": {
          "format": "date-time",
          "type": "string",
          "description": "Start timestamp of the represented interval."
        },
        "userId": {
          "maxLength": 128,
          "minLength": 1,
          "type": "string",
          "description": "Identifier of the related workspace user."
        }
      },
      "required": [
        "end",
        "start"
      ],
      "type": "object",
      "description": "Public API representation of absence."
    }
  },
  "required": [
    "workspaceId",
    "idempotencyKey",
    "data"
  ],
  "additionalProperties": false
}

The schema above is for full. Properties not in the selected profile schema are rejected.

Scope and API operation

Required scopes (all): absences:write, workspace:read. Conditional domain scopes: absences:admin:write; the applicable scopes depend on the request and the stored target. See the linked API operation and scope rules.

• createAbsence — POST /absences

The credential must also satisfy normal workspace authorization and any service-account resource grants. Selecting an MCP tool profile never adds scopes to a credential.

Write preconditions

Concurrency: unconditional. No top-level revision precondition is declared; do not assume conflict protection. Reuse idempotencyKey only for the same creation intent and exact payload.

Output and limits

A compact mutation receipt includes target and revision when available; outcome metadata distinguishes accepted, complete, partial and uncertain results. This tool returns a single API response envelope and is not paginated. The serialized result may not exceed 256 KiB.

Download the exact MCP input and output contract, including profile variants, scopes and safety annotations. Its outputSchema describes the advertised MCP envelope and local $defs; it includes MCP projection metadata in addition to the underlying API schema.

The linked API operation describes the business resource and its field semantics. Write tools preserve their declared revision/idempotency contract and require current permissions. Accepted jobs provide status/resume information; uncertain writes must not be replayed blindly.

Security classification

workspace-mutation: This changes workspace state and may trigger business or external effects. Use its exact scope, revision and idempotency contract; profile selection grants no authority.

The exact safety annotations are {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}. The host and model can still retain tool arguments and results in prompts, logs, or transcripts; use a dedicated least-privilege credential.

Example prompt

Prepare a teamgrid_absence_create operation for my chosen target. Resolve IDs, read current state and revisions, show the intended change, then report its confirmed or uncertain outcome without automatic retries.

The prompt is illustrative. Inspect the proposed tool arguments before approving access to personal, commercial, conversation, or security-configuration data.

Common failures

Authentication failures that prevent the MCP process from starting are covered separately in MCP troubleshooting.

Back to all MCP tools · MCP security model