Skip to main content
Glama
Sign In

OsmO AI Receptionist

by app.getosmo
OverviewDiscussionsAdmin

Cancel a Scheduled Call

cancel_scheduled_call
Destructive

Cancels a call OsmO has booked for later, by callId. Calls booked together are cancelled together. Without confirmed:true nothing is cancelled: it returns confirmation_required naming every call it would cancel. Calls already in progress or finished can't be cancelled.

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": {
      "callId": "<callId>"
    },
    "name": "cancel_scheduled_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
callIdYesA callId from list_scheduled_calls.
confirmedNotrue means the user has approved the confirmation_required preview returned by an earlier call with the same arguments, and carries it out. Without it nothing changes and that preview is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the bar is lower, yet the description adds genuinely new behavior: cancellation is grouped ('calls booked together are cancelled together'), a no-op dry-run mode returns confirmation_required listing every affected call, and finished/in-progress calls are rejected. This is meaningful disclosure beyond the structured flags, though it does not detail permissions or error surfacing.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action, then the grouping rule, then the confirmation gate, then the eligibility limit. Every sentence carries information an agent needs and none repeat the name or title.

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

Completeness5/5

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

Only two parameters, no output schema, and the description still explains the shape of the non-destructive return (confirmation_required naming every call it would cancel). Combined with destructive annotations, an agent has everything needed to call it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description explains what confirmed:true actually commits to (carrying out a preview from an earlier identical call) and that omission yields a no-op preview. That adds semantics about the group-cancellation side effect the schema does not capture.

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?

States a specific verb (cancels) plus the resource and scope constraint ('a call OsmO has booked for later, by callId'), and explicitly excludes in-progress/finished calls, which separates it cleanly from siblings like list_scheduled_calls or get_call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames the two-step flow: without confirmed:true nothing is cancelled and a confirmation_required preview is returned, so an agent knows the precondition before acting. It also states the exclusion (calls already in progress or finished can't be cancelled). It stops short of naming an alternative tool for other outcomes, but the when-to-use/when-not-to-act guidance is explicit.

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

All OsmO AI Receptionist toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources