Skip to main content
Glama
genm
by genm

list_devices

Retrieve a list of SwitchBot devices for management and control through the SwitchBot MCP Server.

Instructions

デバイス一覧を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler for the 'list_devices' tool. It makes a GET request to the SwitchBot API endpoint '/devices' and returns the device list as JSON text content.
    case 'list_devices': {
        const response = await this.axiosInstance.get('/devices');
        return {
            content: [
                {
                    type: 'text',
                    text: JSON.stringify(response.data.body.deviceList, null, 2),
                },
            ],
        };
    }
  • src/index.ts:87-95 (registration)
    Registration of the 'list_devices' tool in the ListTools response, including name, description, and empty input schema.
    {
        name: 'list_devices',
        description: 'デバイス一覧を取得します',
        inputSchema: {
            type: 'object',
            properties: {},
            required: [],
        },
    },
  • Input schema for the 'list_devices' tool: an empty object with no required properties.
    inputSchema: {
        type: 'object',
        properties: {},
        required: [],
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. The description only states what the tool does ('get device list') but doesn't disclose behavioral traits like whether this requires authentication, returns paginated results, has rate limits, or what format the output takes. For a tool with zero annotation coverage, this is inadequate.

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?

Extremely concise single sentence that directly states the tool's purpose. No wasted words or unnecessary elaboration. Perfectly front-loaded with the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero annotations, no output schema, and a simple list operation, the description is incomplete. It doesn't explain what the output looks like (list format, fields included), whether there are any constraints or prerequisites, or how this differs meaningfully from sibling tools. The description provides minimal context beyond the basic action.

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 has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters since there are none. Baseline for 0 parameters is 4, as the description correctly doesn't attempt to document nonexistent parameters.

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?

The description 'デバイス一覧を取得します' (Get device list) clearly states the action (取得/retrieve) and resource (デバイス一覧/device list). It distinguishes from siblings like 'control_device' (which modifies) and 'get_device_status' (which gets status of individual devices). However, it doesn't specify scope (all devices? filtered?) which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description doesn't mention when to use list_devices versus get_device_status (for individual device status) or control_device (for device control). Usage context is implied but not stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/genm/switchbot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server