Skip to main content
Glama

Search clubs and venues

search_venues
Read-onlyIdempotent

Clubs and venues listed on Lineup Atlas, by name, optionally in one city.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNoHow many results (1 to 20, default 10).
queryNoA club or venue name.
localeNoLanguage of the texts and page links (default: en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that results are confined to Lineup Atlas listings and that the city filter accepts only one city at a time, but says nothing about result shape, ordering, or what an empty match returns.

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?

A single sentence that front-loads the resource and then the filters, with no filler or redundancy. Every clause contributes information an agent cannot get from the name alone.

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

Completeness3/5

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

All four parameters are optional and the description plus schema together cover the search axes and the limit/locale defaults. However, there is no output schema, so nothing in either field explains what a venue result contains or how to page beyond the 20-item cap.

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?

Schema coverage is 75%, with the city parameter carrying no inline description. The description compensates by clarifying that city is a single-value, optional filter and that query targets a club or venue name, which is meaningful context for the two parameters that actually drive the search.

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 names the resource precisely (clubs and venues on Lineup Atlas) and the two search axes (name, optionally one city), so an agent can tell it returns venue records. It stops short of differentiating itself from siblings such as search_events or get_city, which is what separates a 4 from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'by name, optionally in one city' suggests the lookup pattern, and 'optionally' signals the city filter is not required. There is no explicit when-to-use versus search or list_cities, and no statement of when this tool would be the wrong choice.

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