Skip to main content
Glama
Sign In
SprutHub MCP Server

SprutHub MCP Server

by pikerr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sprut_list_devices

List smart home devices with their controllable services and current values, optionally filtered by room, to inspect and manage accessories in a SprutHub home.

Instructions

List smart home accessories / devices with their controllable services and current values.

Args: room_id: Optional filter to list devices only in a specific room.

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

Input Schema

NameRequiredDescriptionDefault
room_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses what is returned (services and current values) but does not confirm this is a read-only operation, whether results are paginated, or any permission 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?

Short and front-loaded: purpose in sentence one, the single argument documented immediately after. No filler, though the Args block is slightly formulaic.

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, return-value detail is not required, and the description covers purpose plus the sole argument. The main gap is the absence of any behavioral or safety context for a no-annotation tool.

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 is 0% and room_id has no schema description, but the description compensates by defining it as an optional filter restricting results to a specific room. It adds real meaning beyond the bare 'Room Id' title.

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 (list) and resource (smart home accessories/devices) plus the payload detail (controllable services and current values). Distinguishable from sprut_get_device by implying a collection, though no sibling is named explicitly.

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 through the room_id filter note; there is no statement of when to prefer this over sprut_get_device (single device) or sprut_list_catalog (catalog templates), nor any exclusions. Adequate but leaves routing to inference.

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