Soundcheck Live Event Quotes

Request booking

request_booking

Send a booking / staffing request, including the requester's name, email, and optional phone, to a Soundcheck organization, which creates a lead its team follows up on. Requires organization_id, name, email, event_date, event_type, and location. User confirmation: nothing is sent until the person confirms by email: the call only emails a confirmation link to the address given, and the request reaches the organization after that person opens the email and clicks Confirm.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	the requester's name
`email`	Yes	the requester's email
`phone`	No	the requester's phone
`budget`	No	approximate budget, free-form
`message`	No	what the requester needs (roles, headcount, details)
`location`	Yes	where the event is (city / venue / address)
`event_date`	Yes	the event date (e.g. 2026-07-04)
`event_type`	Yes	the kind of event (e.g. wedding, festival, corporate, concert)
`organization_id`	Yes	the Soundcheck organization to send this booking/staffing request to (slug or id)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	true on success (including confirmation_required prompts)
`data`	No	tool payload (API/composite/confirmation object); object, array, or primitive JSON
`error`	No	when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

removedInput schema / properties / confirmation_token

Removed value: -{
-  "description": "user confirmation. Absent on the first call, which sends nothing and returns a summary plus this token; present only once the person whose details these are has seen that summary and agreed to share them with the organization.",
-  "type": "string"
-}

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / confirmation_token

Added value: +{
+  "description": "user confirmation. Absent on the first call, which sends nothing and returns a summary plus this token; present only once the person whose details these are has seen that summary and agreed to share them with the organization.",
+  "type": "string"
+}

First observedSep 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false). The description adds critical behavior annotations cannot express: nothing is sent until the requester confirms via emailed link, and the request only reaches the organization after the click. That is exactly the kind of non-obvious side effect an agent must know before calling.

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-loaded with the action and effect, then requirements, then the confirmation caveat. Every sentence carries information, though the confirmation flow is stated a little redundantly in two clauses.

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?

With a full input schema, an output schema, and annotations covering safety, the description supplies the one thing structured fields cannot: the deferred, email-confirmed delivery model. Nothing material is missing for correct invocation.

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 all 9 parameters are already documented in the schema; the description merely restates the required set and mentions phone as optional. No new syntax, format, or constraint detail is added, so the baseline 3 applies.

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 ('Send a booking / staffing request ... to a Soundcheck organization') and the concrete effect ('creates a lead its team follows up on'). This clearly distinguishes it from siblings like request_sponsorship or quote_event.

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 a clear trigger context and lists the required inputs, and the double-opt-in flow tells the agent what to expect after calling. It does not explicitly name an alternative tool or state when-not to use it, so it stops short of a 5.

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

All Soundcheck Live Event Quotes 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.