Skip to main content
Glama
Sign In
Xbox AI Controller MCP Server

Xbox AI Controller MCP Server

by SherrySoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

xbox_power_off

Powers off an Xbox console or switches it to Standby/Sleep mode, with an optional target IP address.

Instructions

Powers OFF an Xbox console or puts it into Standby/Sleep mode.

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

Input Schema

NameRequiredDescriptionDefault
ipNoTarget IP address (optional if saved in config).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does usefully disclose the two possible end states (off vs. standby/sleep), which goes beyond the name, but omits which is the default, whether authentication or a wake-capable config is required, and that power-off is disruptive/not trivially reversible.

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?

A single tight sentence with the action and both outcomes front-loaded; every word earns its place.

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, output-schemaless tool this is nearly sufficient, but the unresolved question of how standby vs. off is chosen, and the lack of any auth/reachability note, leaves a real gap for an agent deciding how to invoke it.

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?

Only one optional parameter (ip) exists and schema description coverage is 100%, so the schema already documents it fully. The description adds nothing further about connection/discovery behavior, which is acceptable at baseline.

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 ("Powers OFF an Xbox console") and clearly separates it from the sibling xbox_power_on. However, it leaves ambiguous how the off vs. standby outcome is selected, since no parameter exists for that choice.

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?

Usage is only implied by contrast with xbox_power_on; there is no explicit statement of when to prefer this tool, prerequisites (e.g., device must be reachable/authenticated), or when not to use it.

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