Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seatgeek_venue

Retrieve a SeatGeek venue's full details by numeric ID: address, capacity, timezone, coordinates, and upcoming-event counts. Use for event planning or location analysis.

Instructions

Get a SeatGeek venue's detail. Returns one SeatGeek venue's full detail: address, city/state/country, timezone, capacity, coordinates, and upcoming-event counts. id is SeatGeek's own numeric venue id, obtained from a search or event result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSeatGeek's own numeric venue id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the return payload composition, which is useful, but it does not address not-found behavior, error handling, rate limits, or permissions, leaving the agent guessing on failure modes.

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?

Two tight sentences front-load the verb and resource, then list return fields and id provenance. No filler or schema-redundant detail.

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 one-parameter lookup with no output schema, the description covers what is returned and where the id comes from. A note on invalid/unknown id behavior would make it fully complete, but the simplicity of the tool keeps the gap minor.

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 schema already documents id fully (integer, required), and the description adds the important semantic that this is SeatGeek's own numeric id, not a generic venue id, and that it is obtained from prior search/event results. That provenance helps prevent passing the wrong id.

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?

States a specific verb and resource ('Get a SeatGeek venue's detail') and enumerates the returned attributes (address, timezone, capacity, coordinates, etc.), making the tool's scope obvious. The provenance note about id sourced from a search or event result also separates this lookup from search-oriented siblings like seatgeek_search and seatgeek_venue_events.

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?

Implies a clear invocation path: you need a SeatGeek numeric venue id, which comes from a search or event result. It does not explicitly exclude alternatives (e.g., seatgeek_venue_events for events at a venue) or state when not to use it, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools