Genesis Social

request_reservation

Request a table at a restaurant. THE RESTAURANT IS NOT NOTIFIED YET: the request is held and a confirmation email is sent to the address you provide, and only when that person clicks the link does the restaurant receive it. Tell the user to check their inbox — the link expires in 24 hours. Use a real address belonging to the person you are acting for; the confirmation link is deliberately not returned to you. This is a request, not a confirmed booking: the restaurant confirms out of band.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Name the table is under.
`email`	Yes	The guest's own email — the confirmation link is sent here.
`phone`	No	Optional phone number for the restaurant to reach the guest.
`message`	No	Optional note (occasion, dietary needs, seating preference).
`partySize`	Yes	Number of people (1–30).
`place_slug`	Yes	Restaurant place slug from search_places.
`requestedAt`	Yes	Desired date and time as an ISO instant. Must be in the future.

TDQS

A4.9/5.0

Behavior5/5

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

Despite no annotations, the description fully discloses the request-hold mechanism, email confirmation flow, link expiration, and the out-of-band restaurant confirmation. This is high transparency.

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?

Four sentences, no wasted words. Front-loaded with purpose, then behavioral specifics. Perfectly sized.

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 tool with 7 params and no output schema, the description covers all essential behavioral context: the request-vs-booking distinction, the confirmation process, and email requirements. Agent can use it correctly.

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 baseline is 3. The description adds value by emphasizing that email must be the guest's own and explains the confirmation flow, going beyond schema descriptions.

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?

The description clearly states the purpose (request a table) and explicitly distinguishes it from a confirmed booking, which aligns with sibling tool create_booking. It uses specific verb and resource.

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?

The description provides explicit when-to-use instructions: it is a request, not a confirmed booking; tells user to check inbox; notes email must be real and links expire in 24h. It implicitly differentiates from immediate booking alternatives.

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

All Genesis Social tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct action and domain, with clear descriptions preventing confusion. Similar tools like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are differentiated by service type and workflow.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_categories), ensuring predictability and ease of use for agents.

Tool Count4/5

With 28 tools, the set is fairly large but appropriate for a comprehensive neighborhood directory covering multiple domains (places, events, booking, store, forms, etc.). Each tool serves a distinct purpose without redundancy.

Completeness5/5

The tool surface covers the full lifecycle of common user needs: search and discovery, detailed info, reservations, purchases, and interactions (forms, FAQs). No obvious gaps for the described purpose of a neighborhood directory.

Resources

Need Help?