Skip to main content
Glama

Cancel a scheduled text

cancel_scheduled_text
DestructiveIdempotent

Cancels a scheduled text that has not been sent yet. A canceled text still counts toward this month's and today's limits.

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": {
      "sid": "<sid>"
    },
    "name": "cancel_scheduled_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
sidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructive, idempotent, and open-world behavior, so the description needn't restate those. It adds genuinely non-obvious context: a canceled text still counts toward this month's and today's limits, which affects an agent's decision to cancel versus reschedule. It does not state whether cancellation is reversible or what the response looks like.

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?

Two sentences, zero waste, with the operational precondition front-loaded before the quota side effect. Nothing to trim.

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 one-parameter mutation tool with no output schema, the description covers the precondition and the billing side effect, which is the most important context. It falls short on the identifier semantics — how an agent obtains a valid sid — which is the main thing left unexplained.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter "sid" is undocumented in both schema and description. The agent must infer that sid is the identifier of the scheduled text; no format, source, or retrieval hint is given (e.g., from list_recent_texts or get_text_status).

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 ("Cancels a scheduled text") plus a precondition ("that has not been sent yet"), which implicitly separates it from send_text. It does not name a sibling to route against, but the scope is unambiguous.

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 phrase "that has not been sent yet" tells the agent the applicability condition, but the description offers no explicit when-not guidance (e.g., what to do for an already-sent text, or which sibling to use for rescheduling). Usage is implied rather than spelled out.

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