Skip to main content
Glama

NextUp Walk-in

Get a place

get_place
Read-onlyIdempotent

Details for one place from its slug (from find_walk_in_places): its address, whether it is open now, today's hours, the current wait and how many people are waiting, whether it takes walk-ins and online bookings, its team members, and the link to join the line.

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": {
      "slug": "<slug>"
    },
    "name": "get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe place's slug

Output Schema

NameRequiredDescriptionDefault
nameYes
slugYes
typeNo
addressNo
openNowYes
joinLinkNo
timeZoneNo
waitTextYes
actionUrlYes
localTimeNo
opensTextNo
updatedAtNo
hoursTodayNo
teamMembersNo
topServicesNo
waitMinutesNo
takesWalkInsNo
apptDaysAheadNo
peopleWaitingNo
primaryActionYes
takesBookingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description is not obliged to restate it. The description adds useful behavioral flavor — that the response reflects live state ('open now', 'current wait', 'how many people are waiting') — but says nothing about behavior for an invalid or stale slug, nor about authentication needs. Adequate given annotation coverage, not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is good structure. However, the long enumeration of returned fields (address, hours, wait, team members, link) largely duplicates information already carried by the existing output schema, so a chunk of the sentence does not earn its place.

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?

With an output schema present, the description need not explain return values, and it still characterizes the freshness and scope of the data well. The only real gap is the absence of any error or invalid-slug behavior, which is minor for a one-parameter read tool with clear annotations.

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% for the single parameter, so the baseline is 3. The description goes beyond the schema's bare 'The place's slug' by telling the agent where to obtain a valid slug, which is the one piece of semantics an agent actually needs to supply this required argument correctly.

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 resource and access method: 'Details for one place from its slug', which tells an agent exactly what is fetched and by what identifier. It also references the sibling find_walk_in_places as the source of the slug, aiding disambiguation. The verb is nominal ('Details') rather than an explicit 'retrieve', which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(from find_walk_in_places)' signals this is a follow-up call after a search, which is useful sequencing context. There is no explicit when-not guidance and no mention of the link-oriented siblings (booking_link, join_link), so an agent must infer that this tool is the read path and those are the action paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources