Arranged — Curated Wedding & Event Venue Marketplace

request_curated_quotes

Submit a consolidated rate & availability request for up to 3 shortlisted Gauteng venues. Alerts the venue coordinators directly via email/WhatsApp, creates an escrow quote review session, and returns the actionable client review URL (https://arranged.co.za/quotes?token=...).

Input Schema

Name	Required	Description
`venueIds`	Yes	Array of 1 to 3 venue IDs shortlisted by the client (e.g., ['ven_1', 'ven_2', 'ven_3'])
`eventDate`	No	Estimated or preferred event date (YYYY-MM-DD), or null if flexible
`eventType`	Yes	Celebration type: 'baby_shower', 'wedding', 'birthday', 'year_end', 'corporate', 'private_party'
`clientName`	Yes	The client / host's full name
`guestCount`	Yes	Expected number of guests / attendees
`clientEmail`	Yes	The client's email address to receive quote updates
`clientPhone`	Yes	The client's South African contact phone / WhatsApp number
`dateFlexible`	No	Whether the event date is flexible (defaults to true)
`budgetEnvelope`	No	Estimated budget in ZAR (optional)
`layoutPreference`	No	Layout preference ('indoor', 'outdoor', 'hybrid', 'any')

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 30, 2026

changedInput schema / properties / clientEmail / description

Previous value: -"The client's email address to receive quote updates [Required: non-empty valid value must be supplied]."New value: +"The client's email address to receive quote updates"

changedInput schema / properties / clientName / description

Previous value: -"The client / host's full name [Required: non-empty valid value must be supplied]."New value: +"The client / host's full name"

changedInput schema / properties / clientPhone / description

Previous value: -"The client's South African contact phone / WhatsApp number [Required: non-empty valid value must be supplied]."New value: +"The client's South African contact phone / WhatsApp number"

changedInput schema / properties / eventDate / description

Previous value: -"Estimated or preferred event date (YYYY-MM-DD), or null if flexible [Optional: omit to use server default filter]."New value: +"Estimated or preferred event date (YYYY-MM-DD), or null if flexible"

changedInput schema / properties / eventType / description

Previous value: -"Celebration type: 'baby_shower', 'wedding', 'birthday', 'year_end', 'corporate', 'private_party' [Required: non-empty valid value must be supplied]."New value: +"Celebration type: 'baby_shower', 'wedding', 'birthday', 'year_end', 'corporate', 'private_party'"

changedInput schema / properties / guestCount / description

Previous value: -"Expected number of guests / attendees [Required: non-empty valid value must be supplied]."New value: +"Expected number of guests / attendees"

changedInput schema / properties / layoutPreference / description

Previous value: -"Layout preference ('indoor', 'outdoor', 'hybrid', 'any') [Optional: omit to use server default filter]."New value: +"Layout preference ('indoor', 'outdoor', 'hybrid', 'any')"

changedInput schema / properties / venueIds / description

Previous value: -"Array of 1 to 3 venue IDs shortlisted by the client (e.g., ['ven_1', 'ven_2', 'ven_3']) [Required: non-empty valid value must be supplied]."New value: +"Array of 1 to 3 venue IDs shortlisted by the client (e.g., ['ven_1', 'ven_2', 'ven_3'])"

Changed8 schema fields changedOct 29, 2026

changedInput schema / properties / clientEmail / description

Previous value: -"The client's email address to receive quote updates"New value: +"The client's email address to receive quote updates [Required: non-empty valid value must be supplied]."

changedInput schema / properties / clientName / description

Previous value: -"The client / host's full name"New value: +"The client / host's full name [Required: non-empty valid value must be supplied]."

changedInput schema / properties / clientPhone / description

Previous value: -"The client's South African contact phone / WhatsApp number"New value: +"The client's South African contact phone / WhatsApp number [Required: non-empty valid value must be supplied]."

changedInput schema / properties / eventDate / description

Previous value: -"Estimated or preferred event date (YYYY-MM-DD), or null if flexible"New value: +"Estimated or preferred event date (YYYY-MM-DD), or null if flexible [Optional: omit to use server default filter]."

changedInput schema / properties / eventType / description

Previous value: -"Celebration type: 'baby_shower', 'wedding', 'birthday', 'year_end', 'corporate', 'private_party'"New value: +"Celebration type: 'baby_shower', 'wedding', 'birthday', 'year_end', 'corporate', 'private_party' [Required: non-empty valid value must be supplied]."

changedInput schema / properties / guestCount / description

Previous value: -"Expected number of guests / attendees"New value: +"Expected number of guests / attendees [Required: non-empty valid value must be supplied]."

changedInput schema / properties / layoutPreference / description

Previous value: -"Layout preference ('indoor', 'outdoor', 'hybrid', 'any')"New value: +"Layout preference ('indoor', 'outdoor', 'hybrid', 'any') [Optional: omit to use server default filter]."

changedInput schema / properties / venueIds / description

Previous value: -"Array of 1 to 3 venue IDs shortlisted by the client (e.g., ['ven_1', 'ven_2', 'ven_3'])"New value: +"Array of 1 to 3 venue IDs shortlisted by the client (e.g., ['ven_1', 'ven_2', 'ven_3']) [Required: non-empty valid value must be supplied]."

First observedOct 29, 2026

TDQS

A4/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 that coordinators are contacted via email/WhatsApp, that an escrow quote review session is created, and that a client-facing review URL is returned. It omits idempotency/duplicate-submission behavior, rate limits, and failure modes, which keeps it from a 5.

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?

Two tight sentences, front-loaded with the core action and scope, followed by side effects and return value. Zero filler.

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 10-parameter mutation with no output schema, the description usefully explains the return value (client review URL) and the external side effects, which the schema cannot convey. It leaves gaps around authentication, duplicate-submission handling, and what happens if a venue declines.

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 description coverage is 100%, so the schema already defines all 10 parameters, including the 1-3 venueIds constraint and enums. The description's 'up to 3 shortlisted venues' merely restates the schema and adds no new semantic detail on date, budget, or layout fields.

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 (Submit) and resource (consolidated rate & availability request) with explicit scope: up to 3 shortlisted Gauteng venues. An agent can immediately distinguish this write/notify action from siblings like check_quote_status or find_venues.

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

Usage Guidelines3/5

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

The premise that venues are already shortlisted implies the tool comes after find_venues, but this is left to inference. There is no explicit 'use when / don't use when' guidance, no mention of prerequisites (e.g., valid venue IDs obtained from find_venues), and no note on how it relates to check_quote_status for follow-up.

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

All Arranged — Curated Wedding & Event Venue Marketplace 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?