Pinheiros

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.6/5.0

Behavior5/5

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

Without annotations, the description fully describes behavioral traits: the restaurant is not notified until confirmation, the link expires in 24 hours, and the confirmation link is not returned to the agent. This goes beyond basic purpose and provides critical operational details.

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?

The description is concise and front-loaded with the purpose. Every sentence provides valuable information without repetition. The warnings and instructions are clear and necessary.

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?

Given the tool's complexity (7 parameters, no output schema), the description covers the essential workflow and caveats. It could be improved by explaining what happens on failure or when the link expires, but overall it provides sufficient context for correct usage.

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%, providing good baseline. The description adds meaningful context for the 'email' parameter, explaining it must be a real address and that the confirmation link is sent there. This enhances understanding beyond the schema's description.

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 tool's purpose: to request a table at a restaurant. It distinguishes this from a confirmed booking by emphasizing the email confirmation step and that the restaurant is not notified immediately. This sets it apart 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 Guidelines4/5

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

The description provides explicit usage guidelines, including telling the user to check their inbox, using a real email, and noting that the request is not a confirmed booking. However, it does not explicitly mention when to use this tool versus alternatives like create_booking, though the context implies the difference.

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

All Pinheiros 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.1/5.0

Disambiguation5/5

Each tool targets a distinct operation: bookings, restaurants, events, forms, etc. Even similar actions like create_booking and request_reservation are clearly differentiated by domain and description.

Naming Consistency5/5

Tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_blog_posts). Collection retrieval uses list_ while single item uses get_, which is a standard and clear convention.

Tool Count4/5

28 tools is on the upper end, but each serves a distinct function for a comprehensive neighborhood directory (places, events, booking, forms, etc.). No obvious bloat given the scope.

Completeness5/5

The tool surface covers all major user intents for a local directory: searching places, getting menus, booking services, viewing events, submitting forms, etc. No critical gaps are apparent.

Resources

Need Help?