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.

Input Schema

TableJSON 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

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

A4.2/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile. The description adds value by stating that only outbound messages are returned, that results are newest-first, and that the pagination contract is built around next_cursor, which is not derivable from annotations alone.

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 main content is compact and front-loaded: scope, ordering, filterability, and pagination are conveyed in one efficient sentence. The first 'List messages' line is redundant with the title, so a small deduction is warranted.

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?

With no required parameters, full schema descriptions, strong read-only annotations, and an output schema, the description is complete enough for correct invocation. It gives the essential behavioral context (outbound, newest-first, filters, pagination) without leaving missing call-time information.

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 parameters already have meaningful descriptions. The description summarizes the filter dimensions and cursor behavior but mostly repeats what the schema already says; it adds useful framing but little new parameter-level semantics.

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 names a precise verb and resource ('list recent outbound messages'), and adds scope, ordering, filters, and pagination. It is clearly distinguished from siblings that handle single messages or replies, so an agent can understand which tool to pick.

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 intended use is clear: list recent outbound messages, with optional filters by status/type/recipient/reference and cursor-based pagination. It does not explicitly say when-not-to-use get_message or list_replies, but the resource scope and list behavior are unambiguous enough for selection.

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.