Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Send Sms

send_sms

Sends an SMS to a mobile number, using a minus sign between the international prefix and number, with configurable sender and message body.

Instructions

Send an SMS to a mobile number using minus sign to separate international prefix from the number Args: sender: optional, can be a 11 char long string body: the body of the message string mobile: the recipient mobile number. Eg.:"+39-1234567890"

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

Input Schema

NameRequiredDescriptionDefault
bodyYes
mobileYes
senderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses very little: nothing about irreversibility, whether a message ID is returned, delivery status, throttling, or authentication needs. The one behavioral detail given is the number-format convention, which is useful but far from sufficient for an outbound-send operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and the key format rule is placed up front, but the inline 'Args:' list is loosely formatted and contains contradictory or vague statements (optional vs required sender, 'can be a 11 char long string').

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

Completeness2/5

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

For a no-annotation mutation tool with no output schema and zero schema documentation, the definition should say more about outcomes and side effects. It leaves the agent without knowledge of what a successful call returns or what happens on failure.

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 0%, so the description must compensate, and it does document all three parameters plus a concrete mobile example format and a sender length hint. However, 'body' is defined tautologically and 'sender' is labeled 'optional' while the schema marks it required, which is a meaningful inconsistency.

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 uses a specific verb and resource ('Send an SMS to a mobile number'), so the agent knows exactly what action is performed. It does not differentiate from any alternative tool, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus related tools (e.g. validating a number first), no note on prerequisites, costs, or delivery caveats. Only the bare implied usage of sending a message is present.

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