Skip to main content
Glama

find_multi_game_trips

Read-onlyIdempotent

Supported leagues are NFL, NBA, NHL, MLB, MLS, NCAAF and FIFA. For an explicitly unsupported league such as CFL, NLL, WNBA, F1 or UFC, explain the limit without making a tool call; do not substitute a supported league. Find 2–5 distinct games in one SportCation metro, checked within seven days. City is optional; omit city to search every supported metro. Use canonical city/team slugs when filtering. Search at most 31 inclusive dates within 180 days; trips span at most four local dates. Set max_trip_days=3 for a three-day trip, min_leagues=2 to require two sports, and limit at most 10. Empty results describe only these dates/filters. TBD trips are potential only. Includes SportCation ticket-and-hotel estimates in USD for two adults sharing one room, with explicit partial/unavailable status. No live quotes or best-value ranking. For requests for examples or whether trips exist, apply the named-team and league requirements and present about three suitable options once found, stating the searched dates. Do not scan the full 180 days by default or rescan solely because a result cap was reached. Refine when requirements remain unmet or the user requests broader coverage. Never claim exhaustive coverage from capped results or narrower follow-up filters. Empty truncated results are inconclusive. For weekend requests, flag Monday games as requiring an extra day; describe a holiday extension only when applicable.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "find_multi_game_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNoReturn 1 to 10 trips. Use 5 for an initial shortlist; never request more than 10.
teamsNoCanonical site team slugs; all requested teams must occur. CFB team filters cover configured site team pages.
leaguesNoAllowed leagues. To require both requested sports also set min_leagues=2.
end_dateYes
max_gamesNo
min_gamesNo
start_dateYes
min_leaguesNoRequired distinct leagues; use 2 for an NFL and NHL trip.
max_trip_daysNo

Output Schema

NameRequiredDescriptionDefault
modeYes
tripsYes
coverageYes
orderingYes
returnedYes
truncatedYes
provenanceYes
limitationsYes
generated_atYes
schema_versionYes
excluded_recordsYes
candidates_examinedYes
matching_usable_eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond readOnly/idempotent/non-destructive annotations, it discloses that results include SportCation ticket-and-hotel estimates in USD for two adults, that partial/unavailable status is explicit, that there are no live quotes or best-value ranking, and that TBD trips are potential only. It also warns that capped or truncated empty results are inconclusive and never exhaustive. The one gap is that it doesn't say anything about latency or result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main action is buried mid-paragraph after the supported-league boilerplate, so the description doesn't front-load its core purpose. Several statements are compressed to the point of ambiguity, such as 'TBD trips are potential only' and 'Empty truncated results are inconclusive'. The content is mostly worth keeping, but the ordering and density cost it.

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?

This is a complex 10-param tool with an output schema, and the description covers league support gating, date-window limits, trip-span limits, per-param tuning for the key knobs, estimate provenance, and empty/truncated-result semantics. Given that the output schema handles return values, nothing an agent needs to select or invoke it correctly is 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?

With 40% schema coverage across 10 params, the description compensates well for several: it gives worked values for max_trip_days=3, min_leagues=2, limit at most 10, canonical city/team slugs, and the 31-dates-in-180-days window. But it never explains min_games or max_games, even though the schema defaults them to 2 and 3, so the agent must infer that from the '2–5 distinct games' phrase. Coverage is decent but not complete.

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?

"Find 2–5 distinct games in one SportCation metro, checked within seven days" gives a specific verb (find), a bounded resource (distinct games), and a scope constraint (one metro, seven-day window). This is clearly a multi-game itinerary search, distinct from find_sporting_events and get_trip_details by the plural-games + trip-duration framing.

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 routes around cases: for CFL/NLL/WNBA/F1/UFC it says explain the limit without a tool call and do not substitute a supported league. It states that city is optional and omitting it searches all metros, warns not to scan the full 180 days by default, not to rescan because a cap was hit, and to refine when requirements are unmet.

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.