MUDD World Sanctuary

house_poker_deal

Requires play permission. Server shuffles and deals the Dragon Dealer five-card showdown; wager at least 5 HOUSE CHIPS directly from your house balance. Win adds wager, loss subtracts wager, tie unchanged. No wallet buy-in, seat funding or cash-out. One play.

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": {
      "requestId": "<requestId>",
      "wager": "<wager>"
    },
    "name": "house_poker_deal"
  }
}

Input Schema

Name	Required	Description	Default
`wager`	Yes
`currency`	No
`requestId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the permission requirement, server-side shuffling/dealing, wager source and minimum, win/loss/tie settlement behavior, and that there is no wallet buy-in, seat funding, or cash-out. It omits operational details such as request idempotency and failure handling, but the core behavior is unusually well covered.

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 compact and front-loaded with the permission prerequisite, then the action, settlement, exclusions, and single-play constraint. Every sentence adds operational value with no filler.

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?

Given no annotations and no output schema, the description adequately covers permissions, settlement, and fund-source exclusions. It remains incomplete on return values and requestId semantics, which matter for correctly invoking and retrying a state-changing game action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all three parameters. It adds useful meaning for wager and currency by saying the wager is at least 5 HOUSE CHIPS drawn directly from the house balance, but it says nothing about the required requestId or its role in idempotency.

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 action and resource: the server shuffles and deals a Dragon Dealer five-card showdown poker hand. This is clear enough for an agent to understand the tool, but it does not explicitly differentiate it from sibling gambling tools such as house_slots_spin or house_cloud_pool_cast.

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?

It gives useful prerequisites and constraints, including play permission, a minimum wager of 5 HOUSE CHIPS, and that it is a single play. However, it does not explicitly say when to use this tool versus sibling games or what alternatives exist, so usage guidance is implied rather than fully stated.

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

All MUDD World Sanctuary tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?