Przypominamy.com SMS

Wyślij wiadomość głosową

send_voice

Destructive

Send voice (TTS)

Place a Polish text-to-speech call (max 600 characters; lectors ewa, jacek, jan, maja). Charges prepaid balance. Wait for explicit user confirmation before calling.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Jeden numer, lista numerów (maks. 500) albo grupa kontaktów "group:Nazwa".
`text`	Yes	Tekst do odczytania.
`tries`	No	Liczba prób dodzwonienia się (1–6).
`lector`	No	Głos lektora (domyślnie ewa).
`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.
`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.
`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	Default
`id`	No
`status`	No
`accepted`	No
`messages`	No

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": {
+      "type": "number"
+    },
+    "id": {
+      "type": "string"
+    },
+    "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"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "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

Behavior4/5

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

Beyond the annotations, the description discloses that the operation costs prepaid balance and warns to wait for explicit user confirmation. This adds meaningful behavioral context beyond readOnlyHint, idempotentHint, and destructiveHint. It could mention possible duplicates/retry consequences, but the schema annotations already cover some of that.

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?

The description is compact and well-structured: purpose first, then constraints, then the important confirmation/cost warning. Every sentence earns its place without fluff.

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 9-parameter tool with full schema coverage and an output schema, the description covers the key behavioral prerequisites that are not in structured fields: the Polish TTS nature, the prepaid cost, and the need to wait for explicit user confirmation. An agent can correctly decide to use this tool and invoke it.

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 explains all parameters in detail. The description adds useful semantic context by framing the action as Polish TTS and by noting the 600-character limit and lectors, but most parameter meaning is already present in the schema.

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 clearly states the action and resource: “Send voice (TTS)” and “Place a Polish text-to-speech call.” It also mentions key constraints and lectors, making it easy to distinguish from siblings like send_sms.

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?

It gives clear usage context: the tool places a voice/TTS call, charges prepaid balance, and requires explicit user confirmation before calling. It does not explicitly name a sibling alternative, but the voice-vs-SMS distinction is strongly implied by the title and description.

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.