Skip to main content
Glama

xbox_power_confirm

Confirms a pending Xbox power request with a single-use token, then wakes or sleeps the console, verifies the status change, and switches the TV input after a wake.

Instructions

Carry out the owner's yes. Token: from the latest xbox_power_request, used once, within 30 seconds. Wakes or sleeps the Xbox, says 'not confirmed' until its status shows it, and after a wake switches the TV to the Xbox.

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": "xbox_power_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries the load and does it well: single-use token, 30-second window, returns "not confirmed" until status reflects the change, and the side effect of switching the TV to the Xbox after a wake. Missing only failure behavior on expired token and permission/auth requirements.

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 tight sentences with zero padding, and the token constraints are front-loaded right after the purpose. The opening fragment "Carry out the owner's yes" is a little more mannered than necessary but costs almost nothing.

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; what matters is the token's provenance, validity window and the observable side effects, all of which are covered. Only error paths and authorization expectations are left unstated.

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?

Schema coverage for the single token parameter is 0%, so the description must compensate, and it does: it defines the token's origin (latest xbox_power_request), its lifetime (30 seconds) and its single-use nature. Without this the parameter would be unusable.

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?

"Carry out the owner's yes" is slightly cryptic in isolation, but the following sentence pins it down: it confirms a pending power request and "Wakes or sleeps the Xbox." That verb+resource is specific enough to distinguish it from xbox_power_request, xbox_launch and xbox_status.

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?

States the precondition (token from the latest xbox_power_request), the invocation constraint (used once, within 30 seconds), and thus implicitly when to call it versus xbox_power_request. It never spells out an exclusion or an explicit fallback if the token is stale, so it is clear but not fully exhaustive.

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