Skip to main content
Glama

Get Venue Details

get_venue_details
Read-only

One venue on XP and its upcoming events with all-in prices -- 'what's playing at the Garden this month?'. venue_id comes from search_venues. Tickets to one of those events 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": {
      "venue_id": "<venue_id>"
    },
    "name": "get_venue_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
venue_idYesVenue identifier from search_venues.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that prices are 'all-in' (fees included) and that related ticket data lives in a separate tool. It does not discuss pagination or limits on the upcoming-events list.

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 clauses with zero filler: what it returns is front-loaded, the example query is compact, and the two sibling pointers are packed into single sentences. Nothing is repeated or padded.

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

Completeness5/5

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

With an output schema handling return values, full annotation coverage of safety traits, and only one required parameter, the description supplies everything else an agent needs: what entity it targets, what extra data comes back, and where to go for adjacent needs.

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 coverage is 100% for the single parameter, and the schema's own description already says the venue_id comes from search_venues, so the description's provenance note largely restates structured data. Baseline 3 applies since the schema carries the parameter semantics.

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 specific resource and scope: a single venue plus its upcoming events with all-in prices, illustrated by the quoted question 'what's playing at the Garden this month?'. It lacks an explicit verb (it reads as a noun phrase), and it does not directly distinguish itself from get_event_details, but it clearly delimits venue-level versus ticket-level data.

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 quoted natural-language query gives a concrete usage context, and the description routes the agent to search_venues for the required venue_id and to get_ticket_listings when tickets rather than venue info are wanted. There is no explicit when-not-to-use statement, but the surrounding context is clear.

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