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

Smarter.Poker Model Context Protocol (MCP) Server

Official

get_poker_series_strategy_guide

Read-onlyIdempotent

Provides complete tournament series strategy guides, including structure, late-registration windows, bankroll plans, and venue survival tips, to help players prepare for live events.

Instructions

Returns the complete structure, late-registration window, bankroll plan, and venue survival guide for any major tournament series (wsop-las-vegas, wsop-circuit, wpt-world-championship, wynn-millions, venetian-deepstack, borgata-open, seminole-hard-rock-poker-open, run-good-poker-series, mspt-major, texas-card-house-series) or "first-time-guide" for first-time live poker room etiquette.

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": "get_poker_series_strategy_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoSeries slug or alias (e.g. "wsop-las-vegas", "wsop", "wsop-circuit", "wpt-world-championship", "wpt", "wynn-millions", "venetian-deepstack", "borgata-open", "seminole-hard-rock-poker-open", "run-good-poker-series", "mspt-major", "mspt", "texas-card-house-series", or "first-time-guide"). Omit to list all 10 canonical series guides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.5

TDQS

B3.4/5.0
Behavior4/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 fully covered; the description adds genuine value by naming the content modules returned (structure, late-registration window, bankroll plan, venue survival guide) and confirming the first-time etiquette variant. It does not disclose return format or response size, but with no output schema that omission is minor for a read-only lookup.

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?

One sentence that front-loads the verb and payload content, which is good, but roughly half its length is a parenthetical slug list duplicating the input schema verbatim. The space saved could have carried the missing when-to-use guidance.

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 single optional-parameter, read-only lookup with no output schema, the description covers scope, valid inputs, and the topical contents returned. Only the response shape (document vs. structured object) and the difference from adjacent series tools remain unspecified.

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 the schema already lists every slug and alias plus the 'omit to list all 10 canonical series guides' behavior. The description restates that same enumeration without adding format, defaulting nuance, or alias-resolution rules, so it lands at the baseline.

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?

Uses a specific verb and resource ('Returns the complete structure, late-registration window, bankroll plan, and venue survival guide') and scopes it to a named set of tournament series plus 'first-time-guide', so an agent knows exactly what payload to expect. It stops short of a 5 because it never distinguishes itself from plausible siblings such as get_series_details or search_tournament_series, whose names suggest overlapping territory.

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?

The description enumerates accepted slugs but gives no when-to-use, when-not-to-use, or alternative-tool guidance. An agent cannot tell from this text whether to call this tool or get_series_details / search_tournament_series for series information; the only implied usage is 'first-time-guide' for newcomers, which is thin.

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