Skip to main content
Glama
Sign In

HeyYumi

by ai.heyyumi
OverviewDiscussionsAdmin

Wait for reservation result

wait_for_reservation
Read-only

Wait up to ~25s for the venue to answer a pending reservation. If settled=false, call it again (usually 5 minutes in total, sometimes a few minutes more). When settled=true, tell the user: confirmed = booked; cancelled = the venue declined; expired = no answer in time (offer another time or place).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reservationId": "<reservationId>"
    },
    "name": "wait_for_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
reservationIdYesThe reservationId returned by request_reservation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the crucial long-poll timing (~25s per call), the retry-until-settled loop, and the realistic total wait window. It also enumerates the three terminal outcomes (confirmed/cancelled/expired) with their user-facing meanings, which no structured field provides.

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 tight sentences, front-loaded with the wait duration and scope, followed by the retry rule and the result-mapping rule. No filler and every sentence carries an actionable instruction.

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?

There is no output schema, yet the description explains the settled flag and the full set of status values an agent will encounter. Combined with the polling guidance, nothing needed to call it correctly or interpret its result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single reservationId parameter is already documented as coming from request_reservation. The description says nothing extra about the parameter (e.g., what happens if the ID is unknown or already settled), so baseline 3 applies.

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 with scope: wait up to ~25s for the venue to answer a *pending* reservation, which implicitly separates it from the immediate-return get_reservation sibling. It never names that sibling or explicitly contrasts the two, so the differentiation is inferred rather than stated.

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?

Gives explicit call conditions and the exact retry policy: if settled=false, call again, with an expected total of about 5 minutes and sometimes a few minutes more. It also gives downstream handling instructions for each terminal state, so an agent knows both when to call and what to do with each result.

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

All HeyYumi toolsInspect
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