Skip to main content
Glama

NextUp Walk-in

Find walk-in places

find_walk_in_places
Read-onlyIdempotent

Find businesses in a US city that take walk-ins, with how long the wait is right now. Open places come first, shortest wait first. Optionally narrow to one kind of business with trade: barbershops (barbershop), hair-salons (hair salon), nail-salons (nail salon), brow-and-lash (brow and lash studio), massage-and-spas (massage studio or spa), tattoo-shops (tattoo shop), pet-groomers (pet groomer), vet-clinics (vet clinic), chiropractors (walk-in chiropractor), tax-preparers (tax preparation office), auto-repair (auto repair shop), car-washes (car wash), phone-repair (phone repair shop). Returns at most 10 places, each with its slug, wait and a link to join the line. Start here when you don't have a place's slug yet; use get_place for one place's full details. If nothing is listed in that city (or for that trade), it says so instead of returning places.

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": {
      "city": "<city>",
      "state": "<state>"
    },
    "name": "find_walk_in_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. Austin
stateYesTwo-letter US state code, e.g. TX
tradeNoOptional kind of business, one of the slugs listed in the tool description

Output Schema

NameRequiredDescriptionDefault
cityYes
stateYes
placesYes
messageNo
moreUrlNo
updatedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: result ordering (open first, shortest wait first), a hard cap of 10 places, the fields returned per place, and the no-results message. It stops short of describing freshness of wait data or pagination, but that is a minor gap given the output schema.

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

Conciseness4/5

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

Front-loaded with purpose and ordering, then the trade enumeration, then the sibling routing tip. The long parenthetical slug list is verbose but load-bearing since it is the only place the enum is defined; almost every sentence earns 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?

For a filtered discovery tool with rich annotations and an output schema, the description covers ordering, result cap, per-item contents, empty results, and the hand-off to get_place. The only meaningful omissions are how current the wait times are and whether `trade` is case-sensitive or slug-exact.

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 the baseline would be 3, but the description does real work for `trade`: it supplies the entire allowed vocabulary with human-readable glosses (e.g., 'vet-clinics (vet clinic)'), which the schema only defers to ('one of the slugs listed in the tool description'). City and state get no added semantics beyond the schema examples, keeping this from a 5.

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?

States a specific verb and resource ('Find businesses in a US city that take walk-ins') plus the distinguishing data returned (current wait). It explicitly separates itself from get_place, so an agent can route between the discovery and detail tools without opening either schema.

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 an explicit entry condition ('Start here when you don't have a place's slug yet'), names the alternative for the other case ('use get_place for one place's full details'), and covers the narrowing case via 'trade'. It also states what happens when there is no match, so the agent knows an empty result is normal, not a failure.

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