Skip to main content
Glama

MONO Social

by io.github.junoventures

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
NameRequiredDescriptionDefault
nameYesName the table is under.
emailYesThe guest's own email — the confirmation link is sent here.
phoneNoOptional phone number for the restaurant to reach the guest.
messageNoOptional note (occasion, dietary needs, seating preference).
partySizeYesNumber of people (1–30).
place_slugYesRestaurant place slug from search_places.
requestedAtYesDesired 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?

Fully discloses behavior: request is held, confirmation email sent, restaurant notified only after link click. No annotations exist, so description carries full burden and meets it completely.

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?

Three sentences with zero waste. Purpose, critical constraints, and user guidance are front-loaded and clear.

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?

Explains the request flow and user expectations well. No output schema, so return value is not described. Could mention potential failure modes, but overall complete for the tool's complexity.

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%, so baseline is 3. Description adds value by emphasizing that email must be the guest's own and that the confirmation link is not returned, which is beyond 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?

Clearly states the tool requests a table at a restaurant, with a specific verb and resource. Distinguishes from sibling tools like create_booking by noting this is a request, not a confirmed 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?

Provides clear context: tells user to check inbox, use a real email, and notes the link expires in 24 hours. Implicitly differentiates from confirmed booking tools, but does not explicitly name alternatives.

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

All MONO Social toolsInspect
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 domain action, with clear boundaries between similar operations (e.g., create_booking vs request_reservation vs reserve_event_tickets). Descriptions provide enough context to avoid confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, e.g., create_booking, get_availability, list_events. No mixing of styles or ambiguous verbs.

Tool Count4/5

28 tools is slightly above average but appropriate for a multi-feature neighborhood directory covering bookings, events, movies, menus, forms, etc. Each tool serves a distinct purpose, justifying the count.

Completeness4/5

The tool set covers most expected operations for a directory site: search, details, reviews, booking, events, menus, blog, FAQ, forms, etc. Minor gaps like cancellation or user booking history are acceptable given the domain scope.

Resources