Przypominamy.com SMS

Cennik i warunki

pricing

Read-onlyIdempotent

Pricing

Public SMS price list and terms, no API key needed: per-part price by top-up tier (PLN net, VAT 23%), minimum top-up, free test SMS, international and sender-name rules, how to buy (buy_credits), links to the price list and terms of service.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`links`	Yes
`tiers`	Yes
`currency`	Yes
`how_to_buy`	Yes
`vat_percent`	Yes
`free_test_sms`	Yes
`min_topup_net_pln`	Yes
`price_from_per_sms_part`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and no destructive behavior, so the safety profile is covered. The description adds valuable operational context: it is public, needs no API key, and covers specific pricing rules and terms. It does not describe return format or whether pricing data is live, but an output schema exists.

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 a single dense sentence that front-loads the key facts (public, no API key, SMS price list and terms) before enumerating details. It is largely free of fluff, though the long clause-heavy structure could be slightly more scannable as bullets.

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?

Given the tool's simplicity (zero parameters), the presence of an output schema, and annotations that cover safety, the description provides everything an agent needs: purpose, content covered, no auth requirement, and the buy_credits alternative. No meaningful gaps remain for correct invocation.

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?

The tool takes zero parameters, so there is nothing for the description to clarify about parameter semantics. The baseline for zero params is 4, and the description does not need to compensate for any schema gaps.

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 clearly identifies the tool as a public SMS price list and terms resource, listing the specific pricing details it covers (per-part price, top-up tiers, VAT, minimum top-up, free test SMS, international/sender rules). It distinguishes itself from the sibling buy_credits by noting that this tool explains how to buy rather than performing the purchase. It lacks a strong action verb, but the resource and scope are unambiguous.

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: it is public and requires no API key, and it points to buy_credits for the purchase action, implicitly routing the agent between informational and transactional tools. However, it does not explicitly say 'use this tool when you need pricing information' or list exclusions beyond the buy_credits reference.

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.