# get\_pending\_sms

Returns the signed-in user's current prepared SMS draft, if any. Does not send.

Last updated October 1, 2026

## Access

*   Effect: **Read-only**
*   Required scope: `read` (the `mcp` scope also grants it)

## Example request

The JSON-RPC message an MCP client sends to call this tool. Your client builds it for you; this is for reference and debugging in a tool such as MCP Inspector.

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

Example IDs refer to fictional demo data. Replace them with IDs from your account before calling the real server.

## Description

```
Returns the signed-in user's current prepared SMS draft, if any. Does not send.

Call when the user is revising a draft ("make it shorter", "say tomorrow instead", "change the number") or when you need the exact pending actionId, number, and body before confirm_send_sms.

status none means there is no pending draft — call send_sms to prepare one. status awaiting_confirmation includes actionId plus the exact number and body still waiting for approval. deliveryState provider_uncertain means a send may already be in flight. Do not retry or automatically prepare a replacement. Never treat get_pending_sms as approval to send.
```

## Input parameters

This tool takes no parameters.

Full input schema (JSON Schema)

```json
{
  "additionalProperties": false,
  "type": "object"
}
```

Source: https://financesavi.com/developers/mcp/tools/get_pending_sms
