Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Send a contact SMS

send_contact_sms
Idempotent

Queue one SMS to an existing contact or SMS conversation after the owner reviews the recipient and exact text. Normal site consent, opt-outs, billing and sender readiness apply. Queued is not delivered; inspect list_message_activity for delivery. Reuse the same idempotency_key for retries. This is not a bulk send.

Input Schema

NameRequiredDescriptionDefault
messageYesExact plain-text message for recipient and copy review.
site_idYesThe contact’s site.
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
contact_idNoExisting CRM contact on this site.
conversation_idNoExisting SMS inbox conversation on this site.
idempotency_keyYesStable UUID for this send; reuse unchanged for retries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: queuing is not delivery, consent/opt-out/billing/sender-readiness gates apply, retries must reuse the same idempotency_key, and the owner must have reviewed the recipient and text. This reinforces idempotentHint with actionable retry guidance and discloses the asynchronous delivery model the annotations do not capture.

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?

Five short sentences, front-loaded with the action and scope, then prerequisites, delivery semantics, retry rule, and the bulk exclusion. Every sentence carries decision-relevant information with no filler.

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 mutation tool with no output schema, the description covers the key gaps: delivery is asynchronous, retries need a stable key, consent/billing gates can block sends, and delivery must be checked elsewhere. Nothing an agent needs in order to invoke it correctly appears missing.

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 individual parameter meanings are already documented; the description's contribution is implying either/or targeting between contact_id and conversation_id rather than explaining it directly. It also reinforces idempotency_key reuse, but adds little syntax or selection guidance beyond the schema baseline.

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?

Starts with a specific verb and resource ('Queue one SMS to an existing contact or SMS conversation'), specifies the recipient-review precondition, and explicitly excludes bulk sending. An agent can distinguish this from bulk or campaign-send siblings without opening the 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 clear when-to-use context ('after the owner reviews the recipient and exact text') and a when-not signal ('This is not a bulk send'), plus redirects to list_message_activity for delivery status. It does not name a specific bulk-send sibling as the alternative, so routing is slightly less explicit than it could be.

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

All Mondovo 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