Gigstereo

Request quotes for an event

request_quotes

Send the user's event request to matching providers on Gigstereo, for free: the providers who are interested contact the user directly by WhatsApp or email with their price. It is not a booking and costs nothing. Before calling: (1) collect the details from the user — never invent a name, phone or email; (2) show them a summary and tell them that Gigstereo will share their name and contact details with the matching providers, under the privacy policy https://gigstereo.com/privacy and the terms https://gigstereo.com/terms; (3) call only after they explicitly say yes, with userConsent=true. With targetProviderSlug the request goes to that provider; without it, to the providers of the city.

Input Schema

Name	Required	Description
`city`	Yes	City of the event in Colombia.
`name`	Yes	The user's name.
`email`	No	The user's email. Phone or email is required.
`phone`	No	The user's Colombian mobile/WhatsApp number (10 digits, e.g. 3001234567). Phone or email is required.
`budget`	No	The user's budget in their words, e.g. hasta 800.000 COP.
`details`	Yes	What the user needs, 1-4 sentences (10-1500 characters). Spanish preferred: providers read it.
`category`	No	Service wanted (e.g. mariachi, DJ, fotógrafo) or a slug from list_categories. Required unless targetProviderSlug is given.
`eventDate`	Yes	Event date, YYYY-MM-DD. Not in the past.
`eventTime`	No	Approximate time, e.g. 8:00 p. m.
`eventType`	Yes	Kind of event: boda (wedding), quinceañera, cumpleaños (birthday), serenata, corporativo…
`guestCount`	No	Approximate number of guests.
`userConsent`	Yes	true only if the user saw the summary and the data-sharing notice above and explicitly agreed to send it.
`neighborhood`	No	Neighborhood or venue.
`durationOrSongs`	No	Duration or number of songs, e.g. 1 hora or 10 canciones.
`targetProviderSlug`	No	Slug of the provider the user chose, if they chose one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: the request is free and not a booking, interested providers contact the user directly by WhatsApp or email, and the user's name and contact details are shared under privacy/terms. This is exactly the kind of high-stakes context an agent needs before invoking an openWorld, non-idempotent operation.

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 purpose and uses numbered pre-call steps, which is appropriate for a consent-sensitive operation. The description is somewhat long and repeats the free/no-cost point, but the length is largely justified by the privacy and consent requirements.

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?

Complete for a 15-parameter, consent-sensitive request tool: it explains what happens after the call, how routing works, what must be shown to the user, and why explicit consent is required. No output schema is present, but the description states the provider-contact outcome clearly.

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 description coverage is 100%, so the schema already carries most parameter semantics. The description adds meaningful routing behavior for targetProviderSlug and reinforces the consent requirement, but does not elaborate most of the other 15 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 event request to matching providers on Gigstereo. It clearly distinguishes the action from a booking and explains the outcome, though it does not explicitly contrast with sibling tools such as search_providers or list_categories.

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 explicit preconditions: collect real user details, show a summary and privacy/terms notice, and call only after explicit consent with userConsent=true. It also explains routing with targetProviderSlug versus city-based providers, but does not name sibling tools as alternatives.

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

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