Skip to main content
Glama

Get Event Details

get_event_details
Read-only

The full card for one event on XP: venue, performers, date, images and an all-in price preview. event_id comes from search_events or search_market. The tickets themselves are in get_ticket_listings.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent ID from search_events or a previous user selection (e.g. 406).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the price is an 'all-in price preview' — a useful nuance signaling the figure is indicative rather than a firm quote — but says nothing about error behavior for invalid IDs, freshness of data, or permissions. Adequate given annotation coverage, but not rich.

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?

Three short sentences, front-loaded with the return contents before the ID-sourcing note and the sibling redirect. Every clause carries distinct information with no repetition of the schema or annotations.

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 single-parameter read tool with annotations and an output schema, the description covers what the agent needs: what comes back, where the ID comes from, and which sibling handles tickets. Minor gaps remain around failure modes for an unknown event_id and whether the price preview is live or cached, but these are not blocking.

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 single parameter is documented in the schema itself, so the baseline is 3. The description adds only a mild sourcing hint ('comes from search_events or search_market') versus the schema's 'search_events or a previous user selection'; beyond that it contributes no format or validation detail.

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 names a specific resource (one event's full card) and enumerates its contents: venue, performers, date, images, all-in price preview. It explicitly separates itself from get_ticket_listings, so an agent can distinguish it from the sibling that returns seat inventory 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete routing context: 'event_id comes from search_events or search_market,' which tells the agent how to arrive at a valid call, and it redirects ticket lookups to get_ticket_listings. There is no explicit statement of when this tool should not be used (e.g., for venue-only or seat-map queries), so it stops short of full exclusion guidance.

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