Servana

send_message_to_vendor

Destructive

Use this when the user has chosen a Servana business and asks you to contact it, request a quote, or ask about availability. It sends the user's enquiry to the business; Servana emails the user when the business replies. Pass customer_name and customer_email when the user gave them. To ask several businesses at once (up to 3), put the extra slugs in also_vendor_slugs. Keep the enquiry_refs it returns for check_enquiry_replies. Before calling, show the user the exact message and get their approval, and include their name and an email or phone number. Do not use to confirm a booking or take payment (Servana does neither), or for businesses marked as not accepting AI-assistant messages.

Input Schema

TableJSON Schema

Name	Required	Description
`message`	Yes	The enquiry: what the user needs, when and where, plus the user's name and preferred contact (email or phone) so the business can reply
`vendor_slug`	Yes	The vendor's slug
`customer_name`	No	The user's name, as they gave it. Needed so the business knows who is asking.
`customer_email`	No	The user's email, as they gave it. Servana emails the user a link to read the business's reply. Never invent one.
`customer_phone`	No	Optional phone number, only if the user gave one.
`also_vendor_slugs`	No	Optional: up to 2 more Servana businesses (slugs from search_vendors) to send the same enquiry to. Only when the user asked to contact several businesses and approved the one message for all of them.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / also_vendor_slugs

Added value: +{
+  "description": "Optional: up to 2 more Servana businesses (slugs from search_vendors) to send the same enquiry to. Only when the user asked to contact several businesses and approved the one message for all of them.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 2,
+  "type": "array"
+}

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / customer_email

Added value: +{
+  "description": "The user's email, as they gave it. Servana emails the user a link to read the business's reply. Never invent one.",
+  "type": "string"
+}

addedInput schema / properties / customer_name

Added value: +{
+  "description": "The user's name, as they gave it. Needed so the business knows who is asking.",
+  "type": "string"
+}

addedInput schema / properties / customer_phone

Added value: +{
+  "description": "Optional phone number, only if the user gave one.",
+  "type": "string"
+}

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / message / description

Previous value: -"The enquiry, including the user's name and preferred contact (email or phone) so the vendor can respond"New value: +"The enquiry: what the user needs, when and where, plus the user's name and preferred contact (email or phone) so the business can reply"

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only flag this as a non-read-only, non-idempotent, open-world, destructive action. The description adds substantial context beyond that: Servana emails the user when the business replies, the 3-business fan-out limit, the requirement to show the user the exact message and get approval first, and the exclusion of businesses not accepting AI-assistant messages.

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 the trigger condition and keeps each sentence functional (usage, mechanics, fan-out, follow-up, prerequisites, exclusions). It is dense and slightly long, but no sentence is redundant.

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?

No output schema exists, yet the description explains what the call produces (enquiry_refs to be used with check_enquiry_replies) and the reply flow. For a 6-parameter mutation tool with an open-world side effect, the guidance is complete.

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, but the description adds meaning: pass customer_name/customer_email only when the user provided them, and that also_vendor_slugs brings the total to up to 3 recipients rather than the schema's maxItems of 2. It also ties the returned enquiry_refs to check_enquiry_replies.

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 ('sends the user's enquiry to the business') and scopes the trigger to a chosen Servana business. It clearly distinguishes itself from sibling check_enquiry_replies, which it hands off to via enquiry_refs.

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?

Explicit when-to-use ('user has chosen a Servana business and asks you to contact it, request a quote, or ask about availability') plus explicit when-not ('Do not use to confirm a booking or take payment... or for businesses marked as not accepting AI-assistant messages'). It also names the follow-up tool (check_enquiry_replies) and the prerequisite approval step.

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

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