Skip to main content
Glama
deanxizian

balatro-codex-mcp

by deanxizian

Select current Blind

balatro_select_blind
Destructive

Select the current Blind in Balatro by passing the latest state token, ensuring the action applies to the current game state.

Instructions

选择当前 Blind。所有旧索引在动作后失效。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expected_state_tokenYes最新 state_token;必填。
Behavior3/5

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

The description adds the note '所有旧索引在动作后失效' (all old indexes become invalid after the action), which is a behavioral consequence not captured by the annotations. However, it does not elaborate on other side effects like state token consumption or irreversibility, with annotations already marking this as destructive.

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 exceptionally concise: two short sentences. The first states the purpose, and the second provides a necessary behavioral warning. No filler or redundant content exists.

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 one-parameter action with no output schema, the description provides the essential purpose and an invalidation note. However, it lacks context about game progression (e.g., what happens after selecting a blind) and does not mention when selection is appropriate versus skipping. It is minimally adequate but not thorough.

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?

The schema description fully covers the only parameter expected_state_token ('最新 state_token;必填'), so the tool description adds no additional semantic meaning. Baseline 3 is appropriate given 100% schema coverage.

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 clearly states the action: '选择当前 Blind' (Select current Blind) with a specific verb and resource. It is distinguishable from the sibling 'balatro_skip_blind' by the explicit 'select' wording, though it does not explicitly differentiate itself from alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like balatro_skip_blind. The description assumes game context that an agent may not have, offering no conditions or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deanxizian/balatro-codex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server