Skip to main content
Glama

mister_update_request

Read-only

Requests a MiSTer update via update_all by checking free space and naming a running game, then asks for confirmation before starting anything.

Instructions

Update the MiSTer with update_all. Asks first and starts nothing: checks the free space and names a running game. Read its question aloud.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mister_update_request"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

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, and the description is consistent with that ('starts nothing'). It adds real behavioral detail beyond annotations: the tool checks free space and detects a running game before doing anything, and it tells the agent to relay the resulting question aloud. It does not say what happens if free space is insufficient.

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?

Two short sentences with the action front-loaded and the no-side-effect guarantee immediately after. The closing instruction ('Read its question aloud') is directive but earns its place by telling the agent how to handle the response.

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?

With an output schema present and no parameters, the description needn't explain return values, and it covers the key behavioral preconditions. The one gap is the handoff to the confirm tool and the insufficient-space case, which an agent would need to know.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description appropriately focuses on behavior rather than inventing parameter detail.

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 verb and resource ('Update the MiSTer with update_all') and distinguishes the tool's role as the ask-first stage ('Asks first and starts nothing'), which separates it from mister_update_confirm. It stops short of naming the confirm sibling explicitly, but the staged intent is inferable.

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?

The phrase 'Asks first and starts nothing' implies the caller must follow up with a confirmation step, but the description never names mister_update_confirm or states the condition for proceeding. Usage is implied rather than explicit.

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