Skip to main content
Glama
Sign In
WeMo MCP Server

WeMo MCP Server

by apiarya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_device_status

Retrieve the current power state and device information of a WeMo smart device by name or IP address after network discovery.

Instructions

Get the current status of a WeMo device.

Retrieves the current state and information for a device by name or IP address. The device must have been discovered via scan_network first.

Args:

device_identifier: Device name (e.g., "Office Light") or IP address (e.g., "192.168.1.100")

Returns:

Dictionary containing:
- device_name: Name of the device
- state: Current state ("on" or "off")
- Additional device information

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": {
      "device_identifier": "<device_identifier>"
    },
    "name": "get_device_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_identifierYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A4.2/5.0
Behavior3/5

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

Discloses prerequisite (discovery) and return fields, but lacks details on error behavior, authentication, or side effects. Since no annotations, description carries burden.

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?

Concise, well-structured with Args and Returns sections, no wasted words.

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?

Covers essential information (purpose, prerequisite, return fields). Output schema exists but description is vague on 'additional device information'. Could mention error states.

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 has 0% coverage; description compensates by providing examples (name or IP address) for device_identifier, adding significant meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves current status and information for a WeMo device by name or IP, distinguishing it from siblings like list_devices or show_device_status_ui.

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?

Explicit prerequisite: device must be discovered via scan_network first. No explicit alternatives or when-not-to-use, but context is clear.

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