Skip to main content
Glama

Put someone else on call

add_on_call_override

Business plans: puts a contact on call in a schedule from starts_at to ends_at (up to 90 days), instead of the rotation. Overrides may not overlap. Free.

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": {
      "schedule_id": "<schedule_id>",
      "alert_channel_id": "<alert_channel_id>",
      "starts_at": "<starts_at>",
      "ends_at": "<ends_at>"
    },
    "name": "add_on_call_override"
  }
}

Input Schema

NameRequiredDescriptionDefault
ends_atYesIn the future, after starts_at and at most 90 days later. Overrides of a schedule may not overlap.
starts_atYesWhen the override begins, as an ISO 8601 time.
schedule_idYesSchedule ID from list_on_call_schedules.
alert_channel_idYesThe notification contact on call instead of the rotation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / starts_at / description
      Added value: +"When the override begins, as an ISO 8601 time."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful behavioral constraints beyond them: overrides last at most 90 days and may not overlap, and the feature is limited to Business plans. It still does not explain auth requirements or what happens to the existing rotation during the override.

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?

The description is compact and front-loads the core behavior. The opening 'Business plans:' and trailing 'Free.' are fragmented and slightly cryptic, but they do not obscure the main instruction.

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 four-parameter mutation with full schema coverage and annotations present, the definition covers the key operational constraints and the plan restriction. It does not describe the response or the prerequisite that the contact be confirmed, but nothing essential to invoking it correctly is missing.

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 coverage is 100%, so the input schema already documents all four parameters, including the 90-day and non-overlap constraints on ends_at. The description reinforces the start/end window and the substitution semantics, but adds little meaning beyond the 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 names a specific verb and resource: it puts a contact on call in a schedule for a bounded window instead of the normal rotation. That is enough for an agent to distinguish it from remove_on_call_override and the schedule-management siblings without opening another schema.

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?

The description makes the intended use clear by saying the contact replaces the rotation for the given window. It does not explicitly say when to prefer this over removing or updating an override, nor does it mention any prerequisite such as confirming the notification contact.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources