Przypominamy.com SMS

Lista wiadomości

list_messages

Read-onlyIdempotent

List messages

List recent outbound messages (newest first), filterable by status, type, recipient or reference. Paginate with cursor from next_cursor.

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": "list_messages"
  }
}

Input Schema

Name	Required	Description
`to`	No	Tylko wiadomości na ten numer.
`type`	No	Filtr typu wiadomości.
`limit`	No	Domyślnie 50.
`cursor`	No	Kursor next_cursor z poprzedniej strony.
`status`	No	Filtr statusu, np. delivered albo scheduled.
`reference`	No	Tylko wiadomości z tym reference.

Output Schema

Name	Required	Description	Default
`data`	No	Strona rekordów
`next_cursor`	No	Kursor kolejnej strony

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / type / enum

Previous value: -[
-  "sms",
-  "mms",
-  "vms"
-]New value: +[
+  "sms",
+  "mms",
+  "vms",
+  "whatsapp"
+]

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / status / enum

Previous value: -[
-  "scheduled",
-  "queued",
-  "sent",
-  "delivered",
-  "undelivered",
-  "failed",
-  "expired",
-  "rejected",
-  "cancelled"
-]New value: +[
+  "scheduled",
+  "queued",
+  "sent",
+  "delivered",
+  "undelivered",
+  "failed",
+  "expired",
+  "rejected",
+  "cancelled",
+  "unknown"
+]

Changed1 schema field changedSep 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "data": {
+      "description": "Strona rekordów",
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Kursor kolejnej strony",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedSep 14, 2026
- addedInput schema / properties / cursor / description
```
Added value: +"Kursor next_cursor z poprzedniej strony."
```
- addedInput schema / properties / status / description
```
Added value: +"Filtr statusu, np. delivered albo scheduled."
```
- addedInput schema / properties / type / description
```
Added value: +"Filtr typu wiadomości."
```
First observedSep 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is covered. The description adds real behavioral facts beyond them: results are outbound-only, ordered newest first, and paginated via a cursor returned as next_cursor. It leaves the default page size (50) and page-size ceiling to the schema, which is acceptable.

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, the second front-loading the scope (outbound, newest first) before the filter and pagination notes. The leading 'List messages' line is a redundant echo of the name and title, which is the only wasted text.

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, full parameter documentation and complete annotations, the description only needs to convey scope, ordering and pagination — which it does. Minor gaps: no mention of the 50-item default page size or whether status filters are combined with AND semantics.

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 all six parameters are already documented, including enum values and the cursor semantics. The description only restates the filter dimensions (status, type, recipient, reference) without adding format or edge-case meaning, 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?

The description pairs a specific verb with a specific resource and narrows it: 'List recent outbound messages (newest first)'. The word 'outbound' implicitly separates it from list_replies, but no sibling is named explicitly and the distinction from get_message is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives one concrete operational instruction — paginate using the cursor from next_cursor — which is genuine usage guidance. It never states when this is the wrong tool or which sibling to pick instead (e.g. list_replies for inbound, get_message for a single record).

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.