Skip to main content
Glama

create_on_call_override

Create an on-call coverage override for a roster date range by assigning a covering member, so schedules reflect temporary coverage; write access is required.

Instructions

Create an on-call coverage override for a date range (a roster schedule entry, roster_schedule_span). Requires WRITE_ENABLED=true

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "roster": "<roster>",
      "member": "<member>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "create_on_call_override"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesOverride end (YYYY-MM-DD HH:MM:SS)
nameNoOptional override entry name
startYesOverride start (YYYY-MM-DD HH:MM:SS)
fieldsNoAdditional field values
memberYessys_id of the covering user/member
rosterYessys_id of the roster being overridden

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Optional override entry name",
      +  "type": "string"
      +}
  2. Addedv4.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive, open-world write, so the safety profile is covered. The description adds a genuinely useful operational prerequisite (WRITE_ENABLED=true) that the annotations do not express. It stops short of disclosing how the override interacts with pre-existing schedule entries or whether overlapping overrides are rejected.

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?

Two short sentences with zero padding: the purpose and record type come first, the blocking prerequisite second. Nothing is repeated and nothing needs trimming.

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?

For a six-parameter write tool with full schema coverage and no output schema, the definition covers purpose, record type, and the enablement prerequisite. The remaining gap is behavioral: nothing explains conflict/overlap handling with existing roster entries or what the nested 'fields' object is used for at a semantic level.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including the nested 'fields' object is already documented in the schema. The description only reinforces the start/end date-range concept and adds no new syntax, format, or constraint information beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Create an on-call coverage override') and clarifies the underlying record type ('roster schedule entry, roster_schedule_span'), so an agent knows exactly what object is being written. It does not explicitly contrast itself with the read-oriented sibling 'get_on_call_now', leaving that differentiation to inference.

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?

Usage is implied by the phrase 'for a date range' plus the concrete prerequisite 'Requires WRITE_ENABLED=true', which tells an agent when the call can succeed. There is no explicit statement about when to prefer this over editing a roster directly or using bulk creation, so context is present but incomplete.

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