Convocore

send_sms

Destructive

Send a REAL SMS from the agent's connected SMS number. sendMode=direct (default) sends message as written; sendMode=agent lets the agent write the text (message is then optional). mediaUrls sends MMS. Bills the workspace. For WhatsApp / Messenger / Instagram replies use send_channel_message instead.

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

Input Schema

Name	Required	Description
`to`	Yes	Recipient, E.164.
`from`	No	Optional: a specific connected number. Defaults to the agent's primary SMS number.
`mode`	No	compact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
`agentId`	Yes
`convoId`	No	Optional custom conversation id. Defaults to the recipient digits.
`message`	No	Text to send. Required for sendMode=direct.
`options`	No	Optional per-message agent overrides.
`leadInfo`	No	Optional details about the person (username, email, address, company, notes…) the agent can use to personalize.
`sendMode`	No
`mediaUrls`	No	Up to 10 MMS media URLs.
`campaignId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent and destructive behavior; the description adds materially useful context on top — that it sends a REAL message outside the system and bills the workspace, and that mediaUrls turns it into MMS. It stops short of delivery guarantees, rate limits, or opt-out/compliance handling, which matter for a messaging 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?

Four tight sentences, front-loaded with the core action, then mode semantics, then MMS, then the root alternative. No filler and no repetition of the name or annotations.

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 an 11-parameter, nested-object tool with no output schema, the description covers the highest-risk surfaces (real-send cost, mode selection, MMS). Gaps remain around the mode=compact/full response shaping, the options/leadInfo override objects, and what a successful send returns, though the schema partially covers the former.

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 73%, so several parameters (agentId, options, leadInfo, campaignId, convoId, sendMode) have thin or no schema documentation. The description compensates for the biggest one by fully explaining sendMode semantics and its effect on whether message is required, and links mediaUrls to MMS. It leaves options, leadInfo and campaignId unexplained in both places.

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?

Names a specific verb (send) and resource (SMS) and pins down the scope: a real message from the agent's connected number. It also explicitly separates itself from the channel-based sibling, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use this for SMS/MMS, use send_channel_message for WhatsApp/Messenger/Instagram. It also explains the two sendMode paths (direct = message as written, agent = agent authors the text and message becomes optional), which is exactly the decision an agent must make before calling.

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

All Convocore 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?