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

Smarter.Poker Model Context Protocol (MCP) Server

Official

get_venue_details

Read-onlyIdempotent

Retrieve a poker venue's address, phone, games, table counts, and tournament schedules by venue ID to plan a visit or compare rooms.

Instructions

Retrieve detailed information, address, phone, games offered, table counts, and tournament schedules for a specific poker venue ID.

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": {
      "id": "<id>"
    },
    "name": "get_venue_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric venue ID (e.g. "2499" for Bellagio Poker Room).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description earns credit for disclosing the payload contents (address, phone, games, table counts, tournament schedules), which matters because no output schema exists; it does not say what happens for an unknown or non-numeric ID.

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 front-loaded sentence with the verb and resource first and the returned-field list second; every element carries information and there is no filler.

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 one-parameter read-only lookup with rich annotations and no output schema, the definition covers what it returns and what identifies the venue. The only gap is behavior on a missing or invalid ID, which is a minor omission at this complexity level.

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?

There is only one parameter and schema description coverage is 100%, with the schema itself supplying the format example ("2499" for Bellagio Poker Room). The description's phrase "specific poker venue ID" adds no format, type, or validity detail beyond the schema, so the baseline of 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?

Uses a specific verb ("Retrieve") and resource ("poker venue") and enumerates the exact fields returned: address, phone, games offered, table counts, tournament schedules. It implicitly contrasts with the sibling search tool by specifying "a specific poker venue ID", but never names search_poker_venues as the lookup path.

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 only implied by "for a specific poker venue ID" — an agent can infer this is the follow-up call once an ID is known, but there is no explicit when-to-use statement, no exclusion, and no pointer to search_poker_venues for discovering an ID.

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