Skip to main content
Glama

mister_launch_confirm

Confirms a pending MiSTer game or core launch after the owner explicitly approves it, using the token from the original launch question.

Instructions

Say yes to a start. Only after the owner clearly said yes to the question mister_launch asked. Token: the one that question gave.

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": {
      "token": "<token>"
    },
    "name": "mister_launch_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, so the agent knows this is a mutating action, and the description is consistent with that ('say yes to a start'). It adds the important precondition and token provenance, but does not say what the confirmation actually triggers, whether it is reversible, or what happens if the token is stale.

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?

Three short sentences, front-loaded with the action and followed by the gating condition. The telegraphic style ('Say yes to a start') is slightly terse but nothing is wasted.

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 confirmation tool with an output schema, the description covers the action, the precondition, and the token source. Only the downstream effect of confirming is left unstated.

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 coverage is 0%, so the single parameter 'token' is undocumented in the schema. The description does supply its meaning ('the one that question gave', i.e., issued by the mister_launch question), which compensates for the gap without detailing validation or expiry semantics.

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 specific action (affirm a start, i.e., confirm a pending launch) and ties it to the sibling mister_launch that posed the question. It is clearly a confirmation step rather than a generic mutation, though the word 'start' is vague about what resource is being launched.

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?

Gives an explicit precondition: only call after the owner has clearly said yes to mister_launch's question, and points to that question as the source of the required token. No explicit when-not guidance or named alternatives beyond mister_launch, but the gating condition is unambiguous.

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