Skip to main content
Glama

Przypominamy.com SMS

by io.github.pawelmamcarz
OverviewDiscussionsAdmin

Ustaw domyślną nazwę nadawcy

set_default_sender
Idempotent

Set default sender

Set the account default sender used when send_sms omits from. Name must be active in list_senders. Pass null to restore the platform default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sender_nameYesAktywny nadpis z list_senders albo null, by wrócić do systemowego.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
balanceNoSaldo w PLN
topup_urlNo
sender_nameNo
balance_groszeNo
price_per_voiceNo
price_per_sms_partNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / sender_name / description
      Added value: +"Aktywny nadpis z list_senders albo null, by wrócić do systemowego."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations, the description discloses that passing null restores the platform default and the sender must be active in list_senders. This adds meaningful behavioral context to the write operation implied by readOnlyHint=false and idempotentHint=true.

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 three useful sentences covering purpose, constraints, and null behavior. The opening phrase 'Set default sender' slightly duplicates the title, but the rest is efficient.

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 tool with an output schema and annotations, the description is complete: it covers purpose, applicability, validation, and the null restore case. Nothing critical an agent needs to invoke it correctly 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?

The input schema already documents sender_name as an active list_senders override or null, and schema coverage is 100%. The description adds value by explaining how the parameter interacts with send_sms, which is not fully captured in the schema.

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?

States a specific verb and resource: setting the account default sender. It also clarifies the operational scope by linking to send_sms omitting the from field, which distinguishes it from sibling tools like set_inbound_keyword or set_send_window.

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?

Provides clear context by explaining the default is used when send_sms omits from, and that the given name must be active in list_senders. It does not explicitly name alternatives or exclusions, but the intended usage is evident.

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