Skip to main content
Glama

Event details

event_details
Read-onlyIdempotent

One Las Vegas event by name (e.g. "CES", "SHOT Show", "National Finals Rodeo", "Formula 1"): dates, venue, attendance, what Strip rooms cost those nights against a quiet night, the closest Strip hotels on foot, and official, ticket and page links.

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": {
      "query": "<query>"
    },
    "name": "event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe event name or part of it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety is covered. The description adds genuinely useful scope by spelling out the returned content, including the room-rate-versus-quiet-night comparison, but says nothing about match behavior for partial names, ambiguity handling, or what happens when no event matches.

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

Conciseness5/5

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

A single sentence with the resource and its identifying constraint front-loaded, followed by the return inventory. It is dense but every clause carries information; there is no filler or repetition of the title.

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?

There is no output schema, so the description correctly takes on the job of describing return values, and it does so thoroughly enough to set expectations. What remains thin is the interaction detail — partial-match resolution and no-match behavior — but for a one-parameter read-only lookup the coverage is close to complete.

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% and the single query parameter is documented as 'event name or part of it', so the baseline would be 3. The description earns a bump by supplying concrete example values ("CES", "SHOT Show", "National Finals Rodeo", "Formula 1") that show the expected granularity and phrasing of a query.

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?

Names a specific resource (a single Las Vegas event, looked up by name) and enumerates the payload it returns — dates, venue, attendance, room-rate comparison, nearby Strip hotels, links. That return inventory distinguishes it from list-oriented siblings like whats_on or nightlife, though the description never names an alternative explicitly.

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 reader infers this is for looking up one already-known event by name, while whats_on presumably discovers events. There is no explicit 'use this when / don't use this when' statement, no note about what to do if the name is ambiguous, and no mention of multiple matches.

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