Skip to main content
Glama
Sign In
sts1

sts1

by KeiNodens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

send_command

Execute raw Communication Mod command lines in Slay the Spire to control gameplay, handle prompts, use potions, and retrieve state when dedicated tools do not fit.

Instructions

Send a raw Communication Mod command line.

Commands: PLAY <1-based hand index> [0-based enemy index], END, CHOOSE , CONFIRM, PROCEED, SKIP, CANCEL, RETURN, LEAVE, POTION <use|discard> , STATE, KEY , CLICK , WAIT , START . Prefer the dedicated tools (play_card / end_turn / choose / proceed) — they are easier to get right. PLAY hand index is 1-based, enemy index is 0-based.

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": {
      "line": "<line>"
    },
    "name": "send_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It discloses the raw/format-sensitive nature of the input and the 1-based/0-based index conventions, which is useful behavior context, but says nothing about what happens on malformed commands, error responses, or side effects of game-state-mutating commands like PLAY or POTION.

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?

Purpose is front-loaded and the command grammar earns its space since the schema documents nothing. Only quibble is that the 'prefer dedicated tools' selection cue would be better placed before the long grammar, since it affects whether the agent uses this tool at all.

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?

An output schema exists, so return values need no explanation, and the input contract is fully specified. The remaining gap is failure behavior for invalid or out-of-range command lines, which an agent calling a raw escape-hatch command would benefit from knowing.

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

Parameters5/5

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

Schema coverage is 0% for the single 'line' parameter, so the description must carry everything — and it does: a full grammar for each command plus the critical indexing conventions (PLAY hand 1-based, enemy 0-based). This is exactly the compensating detail the schema omits.

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?

States a concrete verb+resource ('Send a raw Communication Mod command line') and immediately differentiates itself from siblings by naming play_card/end_turn/choose/proceed as preferred alternatives. The enumerated command grammar makes the scope unambiguous, though 'Communication Mod' is jargon an agent must already know.

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

Usage Guidelines4/5

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

Explicitly tells the agent to prefer dedicated tools and why ('easier to get right'), which is real routing guidance. It stops short of saying when this tool IS the right choice (e.g., for POTION, KEY, CLICK, WAIT, START which have no dedicated sibling), leaving that to inference from the command list.

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

Deploy Server

Other Tools