Przypominamy.com SMS

Raport wysyłek

get_report

Read-onlyIdempotent

Delivery report

Aggregate sends by day or month: counts, parts, cost, delivered vs failed. Default last 30 days, max 366. Use for analytics, not live status (get_message).

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

Input Schema

Name	Required	Description
`to`	No	Koniec zakresu, ISO 8601.
`from`	No	Początek zakresu, ISO 8601 (np. 2026-09-01).
`group`	No	Grupowanie (domyślnie day).

Output Schema

Name	Required	Description	Default
`data`	No
`totals`	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": {
+    "data": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totals": {
+      "additionalProperties": {},
+      "properties": {
+        "cost": {
+          "type": "string"
+        },
+        "cost_grosze": {
+          "type": "number"
+        },
+        "count": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds behavioral specifics: aggregation by day or month, default 30-day window, maximum 366-day range, and the fact that it aggregates counts/parts/cost/delivered-vs-failed. This goes beyond the annotations and clarifies the tool's behavior without contradiction.

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 three sentences with no filler. The core purpose and metrics are front-loaded, followed by the time window and the explicit alternative. Every sentence carries meaningful guidance, making it efficient and scannable for an agent.

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?

An output schema exists, so return structure is covered. The description covers the aggregation dimensions, the time-window constraints, the intended use case, and the sibling distinction. For a read-only analytics tool with all parameters documented and annotations providing safety info, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 documents to, from, and group. The description adds meaning by tying 'day or month' to the group parameter and 'default last 30 days' to the implied from/to defaults. This clarifies the parameters' practical usage beyond the schema's enum and format descriptions.

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 a specific verb ('aggregate') and resource ('sends' or delivery report) and lists the exact metrics (counts, parts, cost, delivered vs failed). It explicitly names the sibling tool get_message and contrasts its use case (live status) with this analytics tool, making differentiation immediate without inspecting schemas.

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

Usage Guidelines5/5

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

It explicitly states when to use ('Use for analytics') and when not to ('not live status'), and names the alternative tool (get_message). This gives an agent a clear decision rule, and the default window (last 30 days) and maximum (366) further clarify expected usage scenarios.

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.