Skip to main content
Glama
Sign In

Przypominamy.com SMS

by io.github.pawelmamcarz
OverviewDiscussionsAdmin

Kup doładowanie

buy_credits

Buy credits (top up)

Create a Stripe Checkout payment link for a prepaid top-up in PLN net (min 50, max 5000; VAT 23% added at payment). Bigger top-ups lower the per-part rate (see pricing). Give the link to the user: a human pays by card, BLIK or Przelewy24, the balance updates after payment. Does not charge anything by itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount_pln": "<amount_pln>"
    },
    "name": "buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_plnYesKwota doładowania w zł netto, od 50 do 5000, np. 50, 100, 250 albo 500 (progi cenowe: pricing).

Output Schema

NameRequiredDescriptionDefault
key_noteNo
topup_idNo
amount_netNoKwota netto, np. "100.00 PLN"
status_urlNo
amount_grossNoKwota do zapłaty z VAT
checkout_urlNoLink płatności Stripe Checkout do przekazania człowiekowi
price_per_part_grosze_afterNoStawka za część SMS po zaksięgowaniu

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: it creates a Stripe Checkout link, does not charge by itself, adds VAT at payment, and updates balance only after the human pays. This is exactly the kind of timing, side-effect, and external-flow context needed for a non-idempotent open-world tool.

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 front-loaded with the core action and then adds only operationally relevant details. Every sentence contributes useful context: payment link creation, limits, payment methods, balance update timing, and no direct charge.

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 that the input schema is fully described, annotations cover side-effect flags, and an output schema exists, the description supplies enough operational context for correct invocation. It explains the human-driven checkout flow and payment timing without needing to document return values.

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 coverage is 100% and the single parameter is already well documented in the schema. The description still adds useful meaning by emphasizing PLN net, VAT treatment, and the relationship between larger top-ups and lower per-part pricing.

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 states a specific action and resource: buying credits / creating a Stripe Checkout payment link for a prepaid top-up. It also clarifies scope with currency, limits, and the fact that it does not itself charge money, so an agent can distinguish it from ordinary SMS-sending or account tools.

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?

It gives clear usage context: this is for prepaid top-ups, the link should be given to a human, and payment happens externally by card, BLIK, or Przelewy24. It also points to pricing for volume tiers, though it does not explicitly state when not to use this tool or name a direct alternative beyond the pricing 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 toolsInspect
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.

Resources