Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seatgeek_events_near

Browse SeatGeek events near any coordinate, sorted soonest first, and return one page of results for location-based listings.

Instructions

Browse SeatGeek events near a coordinate. Returns one page of SeatGeek events near a coordinate, soonest first -- the same call its city pages and homepage location-based sections make. Pair with GET /seatgeek/cities for a curated list of coordinates, or pass any coordinate directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
pageNo1-based page number
per_pageNoResults per page, 1-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses pagination ('one page'), ordering ('soonest first'), and that it backs city pages and location-based sections, but it does not describe response contents, defaults, rate limits, or confirm read-only behavior beyond the word 'Browse.'

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?

The description is compact and front-loaded with the core action, then adds sorting, provenance, and a pairing suggestion. It repeats 'near a coordinate' twice, which is minor redundancy, but every sentence otherwise earns its place.

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 paginated list tool, it sufficiently covers required inputs, sorting, pagination behavior, and a workflow for obtaining coordinates. The lack of annotations and an output schema leaves return-field specifics unstated, but an agent has enough to invoke it correctly.

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%, so the schema already documents lat, lon, page, and per_page. The description adds context about coordinates and pairing with cities, but it does not add meaningful syntax, defaults, or format details 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 clearly states the tool browses SeatGeek events near a coordinate and returns one page sorted soonest first, so the verb and resource are specific. It differentiates via the coordinate-based scope and the mention of city-page/homepage usage, though it never explicitly names a sibling it is not.

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 actionable workflow guidance: pair with GET /seatgeek/cities for curated coordinates, or pass any coordinate directly. It does not explicitly state when to prefer this over alternatives like seatgeek_search or seatgeek_venue_events, but the intended use case is clear.

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