Skip to main content
Glama

Przypominamy.com SMS

by io.github.pawelmamcarz
OverviewDiscussionsAdmin

Zapisz szablon

save_template
Idempotent

Save template

Create or update an SMS/MMS/voice template with {{key}} placeholders. Omit id to create. Use list_templates to find existing ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoId istniejącego szablonu tpl_…: pomiń, by utworzyć nowy.
bodyYesTreść z placeholderami {{klucz}}, np. „Cześć {{imie}}, jutro {{kiedy}}”.
nameYesNazwa szablonu, np. „Wizyta”.
typeNoTyp: sms, mms albo vms (głos). Domyślnie sms.
subjectNoTemat MMS; ignorowany dla SMS i VMS.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id istniejącego szablonu tpl_… — pomiń, by utworzyć nowy."New value: +"Id istniejącego szablonu tpl_…: pomiń, by utworzyć nowy."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
  3. Changed5 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"Treść z placeholderami {{klucz}}, np. „Cześć {{imie}}, jutro {{kiedy}}”."
    • addedInput schema / properties / id / description
      Added value: +"Id istniejącego szablonu tpl_… — pomiń, by utworzyć nowy."
    • addedInput schema / properties / name / description
      Added value: +"Nazwa szablonu, np. „Wizyta”."
    • addedInput schema / properties / subject / description
      Added value: +"Temat MMS; ignorowany dla SMS i VMS."
    • addedInput schema / properties / type / description
      Added value: +"Typ: sms, mms albo vms (głos). Domyślnie sms."
  4. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover idempotentHint=true and destructiveHint=false, and the description's 'Create or update' aligns with readOnlyHint=false. The description adds the placeholder syntax and the id-omission rule, which are useful but not extensive; no contradiction with annotations.

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?

Two sentences with no fluff. The purpose is stated immediately, followed by the key operational detail (create vs update) and a pointer to a sibling tool. Highly efficient and front-loaded.

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 presence of an output schema and full parameter descriptions in the schema, the description covers the critical create/update distinction and the placeholder pattern. It points to list_templates for ids, making it complete for an agent to call the tool correctly without additional lookup.

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?

Schema coverage is 100%, so the schema already documents each parameter with examples. The description adds a general placeholder syntax mention and the id-omission rule, but these are also present in the schema's id description. Thus, the description adds minimal value beyond 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?

The description states a clear verb ('Save') and resource ('template'), and clarifies it creates or updates SMS/MMS/voice templates. It distinguishes itself from the sibling list_templates by explicitly referencing it for finding ids, making the tool's purpose 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?

Provides explicit guidance on when to create vs update ('Omit id to create') and directs the agent to list_templates for finding existing ids. It does not explicitly state when not to use this tool (e.g., for listing), but the context is sufficient for basic routing.

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