SMS Vert Pro

send_sms

Envoie un SMS à un ou plusieurs destinataires via SMS Vert Pro. Les numéros doivent être au format international sans le '+' (ex: 33612345678). Un SMS fait 160 caractères ; au-delà, le message part en plusieurs SMS de 153 caractères, chacun facturé (estimation avec count_sms_parts). IMPORTANT : si le compte est en route marketing, la mention 'STOP 36173' doit être ajoutée à la fin du message (obligation légale).

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": {
      "to": "<to>",
      "message": "<message>",
      "sender": "<sender>"
    },
    "name": "send_sms"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Numéros au format international (ex: ['33612345678'])
`delay`	No	Envoi différé (optionnel). Format: 'YYYY-MM-DD HH:MM'
`sender`	Yes	Nom de l'expéditeur (11 car. max, alphanumérique)
`message`	Yes	Contenu du SMS

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 160/153-character billing split, that each segment is charged separately, and a legal compliance rule. It does not mention auth requirements, credit prerequisites (deferred to check_credits), rate limits, or what the send response returns.

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?

Front-loads purpose, then format, then character/billing rules, then the legal caveat in priority order with no filler. It is dense but each sentence adds an operational fact; the only mild cost is cramming billing and legal detail into a single paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers purpose, required input format, billing behaviour, and a mandatory legal step. Remaining gaps (auth, credit checking, return shape, failure modes) are partially covered by sibling tools such as check_credits and get_delivery_report.

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%, so the baseline is 3. The description adds real value beyond the schema by stating the number must omit the '+' prefix (the schema only says 'format international') and by explaining how message length drives segmentation, which is not in the schema at all.

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 ('Envoie un SMS à un ou plusieurs destinataires') and anchors it to the provider ('SMS Vert Pro'). An agent can immediately distinguish it from siblings like cancel_sms, count_sms_parts, or get_delivery_report without opening any schema.

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?

Gives concrete preconditions: numbers in international format without '+', and the legal 'STOP 36173' requirement when the account uses the marketing route. It also routes the agent to count_sms_parts for cost estimation. It stops short of explicit when-not-to-use or alternative routing beyond that single pointer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SMS Vert Pro 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.

Resources

Need Help?