Skip to main content
Glama

Delete an on-call schedule

delete_on_call_schedule
DestructiveIdempotent

Deletes a schedule no escalation policy uses. 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": "delete_on_call_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
schedule_idYesSchedule ID from list_on_call_schedules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful constraint that the schedule must not be referenced by an escalation policy. It omits what error occurs on violation and whether deletion is reversible with any cascade effect; 'Free' is an unclear cost/quota note.

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?

Two very short clauses with the action front-loaded and no filler. 'Free' is terse to the point of ambiguity but not verbose.

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

Completeness2/5

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

For a destructive, presumably irreversible delete with no output schema, the description is thin: failure mode when the schedule is referenced by an escalation policy, cascade effects on overrides, and confirmation expectations are all absent.

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% and the single parameter is fully documented with UUID format and provenance ('from list_on_call_schedules'). The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb and resource ('Deletes a schedule') plus a scope constraint (no escalation policy uses it). It is distinguishable from update_on_call_schedule and delete_escalation_policy by resource, though no sibling is named explicitly.

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 precondition 'no escalation policy uses' implies when deletion is valid, but the description never says what to do when the schedule is in use — no alternative tool or remediation path is offered.

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