Skip to main content
Glama
alcylu

Nightlife Search

get_vip_pricing

Retrieve VIP pricing information for a venue, including minimum spend ranges, zone summaries, and table chart image URL, to help users understand bottle service costs and table reservation options.

Instructions

Get VIP pricing information for a venue. Returns honest weekday and weekend minimum spend ranges, zone summaries, table chart image URL, and booking affordance.

WHEN TO CALL: When a user asks about VIP tables, VIP pricing, bottle service costs, minimum spend, or table reservations at a specific venue.

WHAT TO DO AFTER:

  • Present pricing conversationally ("Weekday minimums start around ¥100K, weekends from ¥200K")

  • Show table chart URL as a layout reference only — do not infer availability from the image

  • If booking_supported is true and user is interested, offer to submit an inquiry via create_vip_booking_request

  • Do NOT suggest specific table codes unless the user asks

  • If busy_night is true, mention the event name and that demand may be higher on that night

  • When pricing_approximate is true, use hedging language ("around", "approximately") rather than stating exact figures

When venue_open is false, the venue is closed on that specific date but general pricing ranges for open nights are still included. Present the open nights and pricing to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venue_idYes
dateNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
venue_idYes
venue_nameYes
venue_openYes
venue_closed_messageYes
pricing_configuredYes
pricing_not_configured_messageYes
weekday_min_spendYes
weekend_min_spendYes
currencyYes
zonesYes
layout_image_urlYes
booking_supportedYes
booking_noteYes
generated_atYes
service_dateYes
event_pricing_noteYes
event_nameYes
busy_nightYes
pricing_approximateYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It covers important behaviors: handling venue_open=false (returns open nights' pricing), pricing_approximate flag (use hedging language), and busy_night (mention event). Missing details on authentication, rate limits, or error cases, but adequate for a read-only tool.

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?

The description is front-loaded with purpose and includes clear 'WHEN TO CALL' and 'WHAT TO DO AFTER' sections. It is somewhat verbose but well-structured. Every section serves a purpose, though some post-call guidance could be considered agent behavior rather than tool definition.

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 existence of an output schema (not shown), the description does not need to explain return values but still summarizes them. It covers edge cases (venue closed, approximate pricing, busy night). Complete enough for a pricing retrieval tool, though missing pagination or request limits.

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

Parameters2/5

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

Schema description coverage is 0% and the description does not explain the parameters (venue_id, date) beyond the context. It does not specify date format, requiredness, or how venue_id is obtained. The description focuses on output and post-call actions rather than input semantics.

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 verb 'Get', the resource 'VIP pricing for a venue', and lists specific returns (minimum spend ranges, zone summaries, table chart URL, booking affordance). This distinguishes it from sibling tools like create_vip_booking_request or get_vip_booking_status, which handle booking operations.

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 'WHEN TO CALL' section explicitly lists scenarios (VIP tables, pricing, bottle service, etc.), providing clear context. However, it does not explicitly state when not to use this tool or suggest alternatives, though the sibling list implies distinctions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alcylu/nightlife-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server