Skip to main content
Glama

Sparetext

Cancel a text

cancel_text
Idempotent

Cancel a text that is still scheduled or waiting for the phone, or with batch_id the rest of a whole send (every text of it still waiting). Once the phone has taken a text (dispatched or sent) it can't be canceled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe text's id, from send_sms
batch_idNoInstead of id: a send's batchId, to stop every text of it still waiting

Output Schema

NameRequiredDescriptionDefault
batchIdNo
messageNo
canceledNo
alreadyOutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / batch_id
      Added value: +{
      +  "description": "Instead of id: a send's batchId, to stop every text of it still waiting",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "id"
      -]
    • addedOutput schema / properties / alreadyOut
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / batchId
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / canceled
      Added value: +{
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "message"
      -]New value: +[]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds the key behavioral rule that cancellation only applies before dispatch, plus the batch-wide scope. It does not state what a cancellation returns or what happens to a batch where some texts already dispatched.

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 sentences, front-loaded with the actionable condition and followed by the exclusion. The batch_id clause is slightly tangled in phrasing but carries no wasted words.

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?

With an output schema and full annotations present, the description only needs to carry the state-based cancellation rule, which it does. It leaves the partial-batch outcome implicit, a minor gap for a tool with this much structured support.

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%, so both parameters are documented in structured fields. The description's mention of batch_id ('the rest of a whole send') restates rather than extends the schema's own wording, so the 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?

States a specific verb (cancel) and resource (text) and constrains it by state: still scheduled or waiting for the phone. An agent can distinguish it from get_message/list_messages, though it does not explicitly contrast with the closest sibling, delete_draft.

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?

Explicit when-to-use and when-not-to-use: it cancels texts still scheduled or waiting, and 'once the phone has taken a text (dispatched or sent) it can't be canceled.' Clear usage context with a hard exclusion, but no named alternative tool for the cases where cancel is impossible.

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