Skip to main content
Glama

Change an on-call schedule

update_on_call_schedule
Idempotent

Business plans. Fields left out keep their value; changing the members, rotation, handoff or time zone starts the rotation over. 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>"
    },
    "name": "update_on_call_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe schedule's name.
rotationNoHow often on call passes to the next member.weekly
time_zoneNoAn IANA time zone.Etc/UTC
member_idsNoNotification contacts (GET /alert-channels) in rotation order. Changing them, the rotation, the handoff or the time zone starts the rotation over with the first member.
handoff_dayNoWeekly handoffs: the weekday, 1 for Monday.
schedule_idYesSchedule ID from list_on_call_schedules.
handoff_timeNoHH:MM on the schedule's own clock.09:00

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"The schedule's name."
    • addedInput schema / properties / rotation / description
      Added value: +"How often on call passes to the next member."
  2. First observed

TDQS

C2.7/5.0
Behavior4/5

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

Annotations already declare the safe-mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false), yet the description still adds real behavior the annotations cannot express: omitted fields retain their values (true PATCH semantics rather than replace), and touching members, rotation, handoff or time zone resets the rotation to the first member. The plan-gating fragment and the dangling "Free." are too vague to count fully as disclosure, and the rotation-reset side effect sits in mild tension with idempotentHint=true if identical calls are repeated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but it is not structured: "Business plans." and "Free." are orphaned sentence fragments with no subject or clear referent, and "Free" reads as leftover documentation boilerplate. The genuinely useful clauses (partial update, rotation restart) are buried after the noise rather than front-loaded.

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

Completeness3/5

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

For a 7-parameter mutation with no output schema, the description covers the two things an agent most needs to avoid harm: that this is a partial update and that certain field changes reset the rotation. It is silent on what a successful response contains, on validation/lookup for schedule_id beyond the schema's pointer to list_on_call_schedules, and on the interaction with overrides already in place.

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 the schema already explains every parameter, including the rotation-reset note on member_ids; the baseline is therefore 3. The description does extend that reset warning to rotation, handoff and time zone collectively and clarifies that absent fields are untouched, which adds a little meaning beyond the schema but does not cover anything the schema leaves undocumented.

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

Purpose2/5

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

The description never states a verb+resource like "updates an existing on-call schedule"; the only purpose signal is indirect, via the enumerated fields (members, rotation, handoff, time zone) and the partial-update clause. The leading fragments "Business plans." and "Free." convey no purpose at all, so the agent must rely on the name and title to know what this does.

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?

"Business plans." is a bare fragment that may hint at an entitlement prerequisite but states nothing explicitly. There is no when-to-use guidance and no routing to siblings such as create_on_call_schedule (for new schedules) or add_on_call_override (for one-off coverage), even though those are the natural confusions for an on-call mutation.

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