Skip to main content
Glama

Search the Market

search_market
Read-only

The same event search as search_events, plus what each event is trading at on XP: its all-in get-in price per ticket and how many fan listings are open to offers on it -- 'tickets to the season opener', 'seats near me under $100'. Suits questions where price is part of the ask; search_events suits finding an event. The fan listings themselves are in list_open_listings.

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_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
cbsaNoMetro area filter (synonyms: city, near me, area).
genreNoGenre filter.
limitNoMaximum number of events to return.
queryYesNatural language event search query.
max_dateNoFilter events on or before this date (YYYY-MM-DD). For relative phrases like 'next month', resolve against _meta.context.today.
min_dateNoFilter events on or after this date (YYYY-MM-DD). For relative phrases like 'this weekend', resolve against _meta.context.today.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds meaningful behavioral context beyond that: it explains that the tool returns per-event market pricing and open fan-listing counts, and clarifies the boundary with list_open_listings for the listings themselves.

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?

The description is front-loaded with the core distinction from search_events, then supports it with concrete query examples and a clear sibling reference. It is appropriately sized and every sentence contributes to selection or scope.

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?

Given the annotations, full schema coverage, and an output schema, the description supplies the remaining decision-critical context: what market data is returned, when to choose it over search_events, and where fan listings live. Nothing essential for correct invocation appears missing.

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 input schema already documents all six parameters. The description gives example natural-language queries but does not add parameter-specific syntax or semantics beyond the schema, which is the baseline-3 case.

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 states a specific verb and resource: it is the same event search as search_events, but additionally returns market data such as all-in get-in price per ticket and count of fan listings open to offers. This clearly distinguishes it from search_events and list_open_listings.

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

Usage Guidelines5/5

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

It explicitly says to use this tool when price is part of the ask and points to search_events for finding an event, while noting that the fan listings themselves are in list_open_listings. The alternatives and selection conditions are clear.

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