Skip to main content
Glama

What's on in Las Vegas

whats_on
Read-onlyIdempotent

Events in Las Vegas between two dates (conventions with their expected attendance, big sports weekends, holidays) and what a typical Strip hotel costs on the nights we checked. Defaults to the next 7 days.

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": "whats_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD; default 6 days after from
fromNoYYYY-MM-DD; default today in Las Vegas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful content context, including event types and hotel cost estimates, but it does not disclose data freshness, pricing accuracy, event coverage, or output granularity beyond the high-level content list.

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?

Two sentences, front-loaded with the main purpose and followed by the default behavior. The parenthetical event examples earn their place, though 'on the nights we checked' is slightly ambiguous and does little work.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry more of the return-value burden. It names the main returned content categories but does not explain the shape, currency, or whether hotel costs are estimates versus live quotes, and it does not clarify boundaries with related sibling tools.

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 description coverage is 100%, and the schema already documents YYYY-MM-DD formats and defaults. The description only restates that dates are accepted and that the default window is 7 days, adding little beyond the schema.

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 states a clear resource and scope: Las Vegas events between two dates, plus typical Strip hotel costs, with a default window. It is specific about content (conventions, sports weekends, holidays, hotel costs) but does not distinguish this tool from siblings such as event_details, hotel_prices, or best_nights.

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?

The default 'next 7 days' gives some usage context, implying a planning or overview use case. However, it gives no explicit when-to-use guidance, exclusions, or alternatives, so an agent must infer whether to call this instead of hotel_prices, event_details, or best_nights.

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