Gracie Barra Jiu-Jitsu

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?

No annotations provided, so description carries full burden. It clearly states the restaurant is not notified until email confirmation, link expires in 24h, and the link is not returned to the assistant. All behavioral traits disclosed.

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?

Description is concise and front-loaded. Every sentence is necessary and informative. No fluff or redundancy.

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?

Given 7 parameters, no output schema, and no annotations, the description fully explains the workflow, email process, and return behavior. It is complete and leaves no critical gaps.

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% (baseline 3). Description adds meaning: specifies email is the guest's own for confirmation, and reinforces request nature. This adds value beyond the schema.

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 states 'Request a table at a restaurant' with clear verb+resource. It explicitly distinguishes from a confirmed booking, differentiating from sibling tools like 'create_booking'.

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 guidance: informs the agent to tell the user to check their inbox, use a real address, and explains the request is not a confirmed booking. It implies alternatives like 'create_booking' for immediate confirmation.

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

All Gracie Barra Jiu-Jitsu 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/5.0

Disambiguation5/5

Each tool targets a distinct resource and action. Even similar operations like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are clearly differentiated by their descriptions and the entities they handle (bookable services, restaurant tables, paid events, free events). No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., create_booking, get_availability, list_events, search_places). This uniform convention makes the tool set predictable and easy for an agent to understand and select from.

Tool Count3/5

With 28 tools, the set is relatively large, exceeding the typical well-scoped range of 3-15. While each tool serves a specific purpose within the neighborhood directory domain, the count feels heavy and may overwhelm simple use cases. A reduction or grouping could improve coherence.

Completeness4/5

The tool set covers a broad range of user-facing operations for a neighborhood directory: searching places, browsing menus, booking services, reserving tables and event tickets, listing products and events, retrieving reviews and FAQs, and submitting forms. Minor gaps exist (e.g., no cancellation or create_review tool), but the core workflows are well-supported.

Resources

Need Help?