Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seatgeek_cities

List SeatGeek's curated metro areas with IDs, names, states, coordinates, and supported verticals (concerts, sports, theater) to pair with events-near queries.

Instructions

List SeatGeek's curated metro areas. Returns SeatGeek's own curated "browse by city" directory (87 metro areas as of 2026-09-15): id, name, state, country, coordinates, and which verticals (concerts/sports/theater) it supports. Each city's lat/lon pairs directly with GET /seatgeek/events-near.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a solid job: it discloses that the list is curated, pins the size at 87 metro areas as of a specific date, and specifies the fields returned. It implies a read-only list operation and avoids any misleading claims, though it does not discuss pagination or response envelope.

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 core action and then add only high-value details: count, fields, and the connection to events-near. No filler or repetition of schema information.

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?

For a no-parameter list tool with no output schema, the description is complete: it names the resource, the scope, the count, the returned fields, and the natural next step. An agent can decide to call it and know what to expect without further clarification.

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 tool has zero parameters and the schema coverage is 100%, so there are no parameter semantics for the description to add. The baseline of 4 applies because the description correctly focuses on what the response contains rather than inventing parameter guidance.

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 opens with a specific verb and resource ('List SeatGeek's curated metro areas') and enumerates the returned fields, making the tool's function unmistakable. The 'browse by city' directory framing and the explicit link to GET /seatgeek/events-near separate it from event/search siblings.

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 clearly identifies the downstream use case: the returned lat/lon pairs feed directly into GET /seatgeek/events-near. It does not explicitly state when not to use it or name alternatives such as seatgeek_search, but for a zero-parameter directory the intended context 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