Skip to main content
Glama

Las Vegas nightlife

nightlife
Read-onlyIdempotent

The main Las Vegas nightclubs, show venues and arenas, where they are, their official sites, and for the big clubs (TAO, Omnia, Hakkasan, LIV, XS, Drai's) the coming week's line-up from the club's own calendar.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nightlife"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 covered. The description adds real value beyond that by disclosing the data source ('from the club's own calendar') and a temporal bound (the coming week), which tells the agent how fresh and how far ahead the line-up data goes. It does not say whether results are cached or how large the payload is.

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?

A single front-loaded sentence that leads with the resource and then layers in location, links, and calendar coverage. The parenthetical club list is long but functional, since it defines the boundary of the line-up coverage. Minor cost: the sentence is a run-on that takes a second pass to parse.

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 no input schema, no output schema, and lightweight annotations, the description carries the burden of describing what comes back, and it does so at a summary level: venues, addresses, official URLs, and weekly line-ups. It omits the concrete shape of a record (field names, whether addresses are structured) and whether line-ups exist for venues outside the six named, leaving a small gap for an agent planning downstream use.

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?

The tool takes no parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate at the input level. The description instead spends its words on output scope, which is the right allocation for a zero-argument tool.

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?

The description names a concrete resource (Las Vegas nightclubs, show venues, arenas) and enumerates the payload: locations, official sites, and a coming week's line-up from the clubs' own calendars for six named venues. That is far more specific than the title alone. It stops short of distinguishing itself from siblings such as whats_on or best_nights, so an agent cannot tell from this text which tool wins for a given query.

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 implied rather than stated: the emphasis on venue directory data plus official sites suggests a lookup/reference tool, and the 'coming week's line-up' clause hints at a calendar role. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for line-up or event queries, which matters given the overlapping sibling names.

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