Skip to main content
Glama

Search Venues

search_venues
Read-only

Find a venue on XP by name, city, state or metro -- 'arenas in Brooklyn', 'venues near me'. Returns venue records, not events; get_venue_details returns a venue's upcoming events.

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": {
      "query": "<query>"
    },
    "name": "search_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city filter (synonyms: near me, area).
limitNoMaximum venues to return.
metroNoOptional metro area filter (synonyms: city, near me, area).
queryYesVenue name or search term.
stateNoOptional state abbreviation (e.g. NY, CA).

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the clarification that results are venue records rather than events, and an output schema is present so return values need no explanation. Useful but minimal added context beyond the annotations.

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 compact sentences with the core search capability front-loaded, followed by the disambiguation clause. No filler, no repetition of schema 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 five-parameter read-only search with full schema coverage, annotations, and an output schema, the description covers purpose, scope, and sibling routing adequately. It omits nothing critical, though it does not mention result ordering or how the limit parameter affects paging behavior.

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 every parameter (query, city, state, metro, limit) is documented in the schema including synonym hints. The description restates the same filter dimensions without adding syntax, format, or precedence guidance (e.g., how city and metro interact), so the baseline 3 applies.

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 ('Find a venue on XP') plus the exact search dimensions (name, city, state, metro) and two concrete query examples. It also draws the boundary against get_venue_details ('returns venue records, not events'), so an agent can distinguish it from siblings without opening any 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?

Gives example queries that show the intended use ('arenas in Brooklyn', 'venues near me') and explicitly routes event lookups to get_venue_details. It stops short of stating when this tool should not be used (e.g., for ticket listings or market data, where other siblings apply), leaving a small inference gap.

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