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.

Input Schema

TableJSON 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"}.
`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

TableJSON 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.

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.3/5.0

Behavior5/5

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

The description adds significant behavioral context beyond the annotations: it discloses billing impact ('Charges prepaid balance (parts × account rate)'), the need for explicit user confirmation, and the consequence of being a 'real billed send.' This directly complements the destructiveHint=true annotation and gives the agent critical safety-relevant information.

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?

The description is compact: two short sentences following the redundant title repeat 'Send SMS.' It front-loads the core function and then delivers the billing/confirmation warning. The redundancy of repeating the tool name is minor, and every substantive sentence earns its place.

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?

Given the 11-parameter schema with full coverage and an output schema, the description only needs to highlight usage-critical context, which it does: recipient scope, billing, prerequisite counting, and user confirmation. It does not delve into optional parameters like send_at or priority, but those are already fully documented in the schema, so this is not a gap.

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 parameter semantics baseline is 3. The description restates the 'to' parameter's scope ('one number, a list (max 500), or a contact group') and mentions 'parts × account rate,' but adds no deeper meaning beyond what the schema already provides. It does not need to compensate for missing schema info.

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?

The description uses a specific verb and resource: 'Send an SMS to one number, a list (max 500), or a contact group.' It clearly identifies recipient types and scope, and the presence of sibling send_voice makes the distinction obvious. The tool's purpose is immediately understandable 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 description gives explicit usage context: 'Call count_sms_parts first, then wait for explicit user confirmation: this is a real billed send.' This tells the agent the required precondition and a clear when-to-use signal. It does not explicitly mention when not to use the tool or compare against send_voice, but the two are distinct enough that the guidance is sufficient.

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.