Przypominamy.com SMS

Ustaw domyślne godziny wysyłki

set_send_window

Idempotent

Set send window

Set the account default sending hours in Europe/Warsaw, e.g. 08:00-20:00. Out-of-window sends are deferred to the next window start. Pass null for no limit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`send_window`	Yes	Okno „HH:MM-HH:MM” w czasie polskim, np. „08:00-20:00”, albo null bez limitu.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No
`balance`	No	Saldo w PLN
`topup_url`	No
`sender_name`	No
`balance_grosze`	No
`price_per_voice`	No
`price_per_sms_part`	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": {
+    "balance": {
+      "description": "Saldo w PLN",
+      "type": "string"
+    },
+    "balance_grosze": {
+      "type": "number"
+    },
+    "id": {
+      "type": "string"
+    },
+    "price_per_sms_part": {
+      "type": "string"
+    },
+    "price_per_voice": {
+      "type": "string"
+    },
+    "sender_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topup_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 14, 2026

addedInput schema / properties / send_window / description

Added value: +"Okno „HH:MM-HH:MM” w czasie polskim, np. „08:00-20:00”, albo null bez limitu."

First observedSep 14, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds useful behavior beyond annotations: out-of-window sends are deferred to the next window start, and null removes the limit. This is not derivable from the schema or annotations and helps the agent understand consequences.

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 and front-loaded, with no wasted detail. The opening 'Set send window' repeats the tool name, but the remaining sentences each provide useful information.

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 single-parameter idempotent setter with an output schema, the description includes everything needed: timezone, format, null semantics, and deferral behavior. There are no obvious missing details.

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?

The input schema already fully documents the parameter format, timezone, and null option, so the description adds little to parameter semantics. The example and deferral behavior provide context, but do not significantly extend the parameter meaning.

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 uses a specific verb, 'set', and resource, 'account default sending hours,' making the operation clear. It does not explicitly differentiate from sibling tools, but the send-window resource is distinct enough that the agent can identify the tool's purpose.

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 provides clear context by specifying that this sets account default sending hours in Europe/Warsaw. It does not name alternatives or exclusions, but the narrow scope makes the intended usage reasonably obvious.

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.