Skip to main content
Glama

Create an on-call schedule

create_on_call_schedule

Business plans: a rotation through notification contacts (list_notification_contacts), handing off daily or weekly at a time in a time zone. The first member is on call from now. 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": {
      "name": "<name>"
    },
    "name": "create_on_call_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe 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.
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.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds two genuine behavioral facts beyond that: the plan requirement and that the first member is on call starting now. It says nothing about what happens on duplicate names, what the success response contains, or partial-failure behavior, so the addition is real but thin.

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?

It is commendably short and leads with the plan and rotation concept, but the telegraphic style costs clarity: 'Free.' hangs as an unexplained fragment, and 'Business plans:' is a label rather than a sentence. Nothing is padded, yet the compression forces the reader to guess at meaning.

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 6-parameter creation tool with no output schema, the description covers the domain concept and starting state but omits the return value entirely (e.g., whether a schedule ID comes back) and gives no error or validation context. Annotations and the 100%-covered schema carry most of the burden, so the gap is moderate rather than severe.

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 name, rotation, time_zone, member_ids, handoff_day, and handoff_time in detail, including the restart-the-rotation rule. The description only adds that member_ids come from notification contacts and points at the list_notification_contacts tool, which is modest incremental value over the schema's own endpoint reference. Baseline 3 is appropriate.

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

Purpose3/5

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

The description names the resource and its core mechanics (a rotation through notification contacts, daily or weekly handoffs in a time zone) but never states the verb. It relies on the title to convey 'create', and it does not distinguish itself from update_on_call_schedule or add_on_call_override, which share the same domain vocabulary.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of how this differs from update_on_call_schedule. The parenthetical pointing at list_notification_contacts is a useful prerequisite hint for sourcing member IDs, but the 'Business plans:' fragment only implies a plan-gating condition without explaining what an agent or user should do if the plan doesn't qualify.

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