Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

cancel_scheduled

Cancel a scheduled SMS send or queued bulk job before it starts; unsent messages are removed and their price is returned to credit.

Instructions

Cancel a scheduled send (or a queued bulk job that has not started yet). Unsent messages are removed and their price is returned to credit.

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": {
      "jobId": "<jobId>"
    },
    "name": "cancel_scheduled"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesjobId returned by send_sms / send_bulk_sms with send_at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key side effects: unsent messages are removed and their price is returned to credit. It does not cover failure behavior for an already-started job, permissions, or idempotency of repeated cancels, which leaves some behavioral gaps.

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 short sentences with zero filler, front-loading the action and following with the effect on messages and credit. Every clause carries information an agent needs.

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 single-parameter cancellation tool with no output schema, the description covers purpose, scope, and consequence well. The remaining gap is failure handling when the target job is no longer cancellable, which matters for a destructive-style operation.

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?

Only one parameter, and the schema already documents it at 100% coverage as the jobId returned by send_sms / send_bulk_sms with send_at. The description adds no additional meaning about the identifier beyond what the schema states, so the baseline of 3 applies.

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 (Cancel) and two specific resources (a scheduled send, a queued bulk job), plus a scoping condition ('has not started yet') that separates it from the send_* and get_* siblings. An agent can identify the operation without opening the schema.

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?

The parenthetical 'queued bulk job that has not started yet' and the scheduled-send framing implicitly define when the tool applies and when it does not (a started or already-sent job is out of scope). It stops short of stating explicitly what to do if the job has already begun, but the context is clear.

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