Skip to main content
Glama
Smarter.Poker Model Context Protocol (MCP) Server

Smarter.Poker Model Context Protocol (MCP) Server

Official

search_tournament_series

Read-onlyIdempotent

Search poker tournament series, championship festivals, and tours by name, venue, tour, or upcoming status to find relevant events.

Instructions

Search poker tournament series, championship festivals, and tours (WSOP, WPT, MSPT, RGPS, PGT, DeepStack).

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

Input Schema

NameRequiredDescriptionDefault
tourNoTour abbreviation (e.g. "WSOP", "WPT", "MSPT", "RGPS", "PGT", "DSE").
limitNoMaximum number of results to return (default: 10, max: 50).
searchNoSearch query for series title, tour, or host venue (e.g. "Venetian", "World Series of Poker", "WPT").
upcomingNoFilter for upcoming or active series only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds no behavioral context beyond naming the covered tours — nothing about result ordering, pagination, or empty-result behavior — so it earns little credit beyond the structured fields.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; verb and resource come first and the tour examples are compact. It is appropriately sized, though it spends its only content on enumeration rather than routing detail.

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?

For a simple four-parameter read-only search tool with full schema coverage and no output schema, the definition is minimally adequate. It never indicates what a result record contains or how matches are ranked, which leaves the agent guessing about return shape.

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 each of the four parameters is documented in the schema, including the limit default/max and the upcoming enum values. The description adds no parameter meaning beyond that, so baseline 3 applies.

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 states a specific verb ("Search") and a concrete resource (poker tournament series, championship festivals, tours) and enumerates covered tours like WSOP, WPT and MSPT. It does not distinguish itself from adjacent siblings such as get_series_details or search_poker_venues, so an agent must infer the boundary from names alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no stated prerequisites, and no exclusions. The only usage signal is the implicit 'search by series/tour/venue' conveyed by the name and schema, leaving routing decisions to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.