Przypominamy.com SMS

Wyślij SMS

send_sms

Destructive

Send SMS

Send an SMS to one number, a list (max 500), or a contact group. Charges prepaid balance (parts × account rate). Call count_sms_parts first, then wait for explicit user confirmation: this is a real billed send. Requires purpose. No balance: the error contains a payment link; see buy_credits.

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": {
      "to": "<to>",
      "purpose": "<purpose>"
    },
    "name": "send_sms"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Jeden numer, lista numerów (maks. 500) albo grupa kontaktów "group:Nazwa".
`from`	No	Nazwa nadawcy (nadpis). Pomiń, by użyć domyślnego nadpisu konta. Dostępne nazwy: list_senders.
`text`	No	Treść wiadomości (do 1000 znaków, dzielona na części); pomiń, gdy podajesz template_id. Placeholdery: {{imie}}, {{nazwisko}}, pola własne kontaktu, {{opt_out}} = osobisty link wypisu (wymagany w SMS-ach marketingowych), {{link:https://…}} = śledzony krótki link z licznikiem kliknięć (maks. 2).
`params`	No	Wartości do szablonu, np. {"imie":"Anno","kiedy":"jutro 10:00"}.
`purpose`	Yes	Cel wysyłki, krótko i zgodnie z prawdą (5-200 znaków), np. „przypomnienie o wizycie”, „kod logowania”, „potwierdzenie zamówienia”. Wymagany; zapisywany przy wiadomości.
`send_at`	No	Zaplanowana wysyłka, data ISO 8601 (np. 2026-09-08T09:00:00+02:00). Maks. 90 dni w przód. Pomiń, by wysłać teraz.
`priority`	No	SMS priorytetowy (osobna kolejka dla kodów i alertów, podwójna cena).
`reference`	No	Własny identyfikator (np. numer zamówienia) do odszukania wiadomości później.
`expires_at`	No	ISO 8601: po tym czasie dostawca przestaje próbować doręczyć (15 min – 72 h po wysyłce). Np. termin wizyty, po którym przypomnienie nie ma sensu.
`send_window`	No	Okno godzin wysyłki w czasie polskim, np. "08:00-20:00". Poza oknem wysyłka jest przesuwana na najbliższy początek okna. Pomiń, by użyć ustawienia konta.
`template_id`	No	Id szablonu (tpl_…) z list_templates zamiast text; {{klucz}} w szablonie podstawiane z params.
`idempotency_key`	No	Unikalny identyfikator zatwierdzonej wysyłki. Przy ponowieniu zachowaj tę samą wartość; nie zmieniaj po timeoutcie.

Output Schema

Name	Required	Description
`sent`	Yes
`failed`	Yes
`accepted`	Yes	Ile wiadomości przyjęto do wysyłki
`messages`	Yes
`total_cost`	Yes	Suma PLN, np. "0.30 PLN"
`rejected_blacklist`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / properties / purpose

Added value: +{
+  "description": "Cel wysyłki, krótko i zgodnie z prawdą (5-200 znaków), np. „przypomnienie o wizycie”, „kod logowania”, „potwierdzenie zamówienia”. Wymagany; zapisywany przy wiadomości.",
+  "maxLength": 200,
+  "minLength": 5,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "to"
-]New value: +[
+  "to",
+  "purpose"
+]

Changed1 schema field changedSep 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "accepted": {
+      "description": "Ile wiadomości przyjęto do wysyłki",
+      "type": "number"
+    },
+    "failed": {
+      "type": "number"
+    },
+    "messages": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "cost_grosze": {
+            "type": "number"
+          },
+          "id": {
+            "description": "Id wiadomości msg_…",
+            "type": "string"
+          },
+          "parts": {
+            "type": "number"
+          },
+          "status": {
+            "description": "queued, sent, delivered, …",
+            "type": "string"
+          },
+          "to": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rejected_blacklist": {
+      "type": "number"
+    },
+    "sent": {
+      "type": "number"
+    },
+    "total_cost": {
+      "description": "Suma PLN, np. \"0.30 PLN\"",
+      "type": "string"
+    }
+  },
+  "required": [
+    "accepted",
+    "sent",
+    "rejected_blacklist",
+    "failed",
+    "total_cost",
+    "messages"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 14, 2026

changedInput schema / properties / to / anyOf

Previous value: -[
-  {
-    "description": "Numer telefonu w formacie E.164, np. +48533991881. Numer 9-cyfrowy bez prefiksu = Polska.",
-    "type": "string"
-  },
-  {
-    "description": "Grupa kontaktów: \"group:<id lub nazwa>\", np. \"group:VIP\". Członkowie dostają personalizację {{imie}}, {{nazwisko}} i pól własnych.",
-    "pattern": "^group:.+",
-    "type": "string"
-  },
-  {
-    "items": {
-      "anyOf": [
-        {
-          "description": "Numer telefonu w formacie E.164, np. +48533991881. Numer 9-cyfrowy bez prefiksu = Polska.",
-          "type": "string"
-        },
-        {
-          "description": "Grupa kontaktów: \"group:<id lub nazwa>\", np. \"group:VIP\". Członkowie dostają personalizację {{imie}}, {{nazwisko}} i pól własnych.",
-          "pattern": "^group:.+",
-          "type": "string"
-        }
-      ]
-    },
-    "maxItems": 500,
-    "minItems": 1,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "Phone number in E.164. Example: +48533991881. A 9-digit number without prefix is treated as Polish.",
+    "type": "string"
+  },
+  {
+    "description": "Grupa kontaktów: \"group:<id lub nazwa>\", np. \"group:VIP\". Członkowie dostają personalizację {{imie}}, {{nazwisko}} i pól własnych.",
+    "pattern": "^group:.+",
+    "type": "string"
+  },
+  {
+    "items": {
+      "anyOf": [
+        {
+          "description": "Phone number in E.164. Example: +48533991881. A 9-digit number without prefix is treated as Polish.",
+          "type": "string"
+        },
+        {
+          "description": "Grupa kontaktów: \"group:<id lub nazwa>\", np. \"group:VIP\". Członkowie dostają personalizację {{imie}}, {{nazwisko}} i pól własnych.",
+          "pattern": "^group:.+",
+          "type": "string"
+        }
+      ]
+    },
+    "maxItems": 500,
+    "minItems": 1,
+    "type": "array"
+  }
+]

First observedSep 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the destructive/openWorld/non-idempotent annotations by disclosing the cost model (parts × account rate, prepaid balance), the mandatory human-confirmation ritual for a real billed send, and the recovery path on insufficient balance. This is exactly the billing-and-irreversibility context annotations cannot convey.

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?

Five short sentences, zero filler. The refund-relevant warning (billed send, confirm first) is front-loaded before the prerequisites and error path, matching the order an agent needs.

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?

For a 12-parameter, high-stakes, billed mutation with an output schema, the description supplies the missing decision context — cost, confirmation gate, prerequisite call, and out-of-credit handling — while leaving parameter detail to a fully described schema.

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 description coverage is 100%, so the schema already documents all 12 parameters in detail (recipient formats, template_id vs text, send_window, expires_at, idempotency_key). The description only echoes the 500-recipient cap and the required purpose, adding little beyond the structured fields — baseline 3.

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?

Specific verb + resource ("Send an SMS") plus the exact accepted recipient shapes: single number, list capped at 500, or a contact group. This distinguishes it cleanly from siblings like send_voice, count_sms_parts, and save_template without needing 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 Guidelines5/5

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

Explicit sequencing: call count_sms_parts first, then obtain explicit user confirmation before sending. It also names the failure path (no balance → error contains payment link → see buy_credits) and a prerequisite (purpose required), leaving nothing to inference.

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

All Przypominamy.com SMS tools Inspect

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.