Skip to main content
Glama

Remove an override

remove_on_call_override
DestructiveIdempotent

Removes an override from a schedule (its id is in the schedule's overrides). 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>",
      "override_id": "<override_id>"
    },
    "name": "remove_on_call_override"
  }
}

Input Schema

NameRequiredDescriptionDefault
override_idYesThe override's id, from the schedule's overrides in list_on_call_schedules.
schedule_idYesSchedule ID from list_on_call_schedules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / override_id / description
      Added value: +"The override's id, from the schedule's overrides in list_on_call_schedules."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds one trait not in the annotations, "Free," which tells the agent there is no billing impact. It does not say what happens to the schedule after the override is removed (for example, whether the original rotation resumes) or whether the removal is reversible, which is the main behavioral gap.

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 short sentences, front-loaded with the action and resource, with no filler. The one-word "Free." sentence is terse but carries distinct information rather than repeating the schema.

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 simple two-parameter destructive operation whose annotations already carry the safety hints and whose schema fully documents both ids, the description covers what an agent needs to select and call it. The only omission is the resulting state of the schedule after removal, which is a minor rather than blocking gap.

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 baseline is 3. Both parameters are already documented as UUIDs sourced from list_on_call_schedules, and the description only restates that the override id comes from the schedule's overrides without adding format or constraint detail beyond the schema.

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?

States a specific verb and resource: "Removes an override from a schedule." The parenthetical identifies which object the override id belongs to, which separates it cleanly from add_on_call_override. It stops short of naming a contrasting sibling or stating scope limits, so it is not a 5.

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 only implied: you remove an override that is no longer wanted. The clause "its id is in the schedule's overrides" usefully explains how to obtain the required id, but there is no explicit when-to-use/when-not guidance or comparison against alternatives such as updating the schedule instead.

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