SprutHub MCP Server

by pikerr

Overview Schema Source Related Servers Discussions Admin

Python

Local

sprut_create_room

Create a new room in a SprutHub smart home by specifying its name to organize and control devices by space.

Instructions

Create a new room in the smart home.

Args: name: Name for the new room.

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

Input Schema

Name	Required	Description	Default
`name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about required permissions, what happens when a room name already exists, whether the operation is idempotent, or what state the new room starts in. An output schema exists, so return format is partially covered, but the mutation semantics remain undisclosed.

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?

The purpose sentence is front-loaded and the 'Args' block is compact. The argument line is largely redundant with the schema title 'Name', but it costs little and the overall definition is not bloated.

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?

For a no-annotation mutation tool that is part of a CRUD room family, the description omits prerequisites, duplicate-name behavior, and any linkage to update/delete/list siblings. The presence of an output schema excuses it from describing return values, but the gaps elsewhere leave it thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there is one parameter, so the description is the only source of parameter meaning. It merely restates the field ('name: Name for the new room') without adding constraints such as uniqueness, length, or whether the name is free-form or must be unique across rooms.

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 ('Create a new room'), so an agent immediately knows this is a creation operation. It does not, however, distinguish itself in the description from siblings like sprut_update_room or sprut_delete_room, leaving that differentiation to the tool name alone.

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?

The description offers no when-to-use guidance and never references the closely related siblings (sprut_list_rooms, sprut_update_room, sprut_delete_room). An agent must infer that this is the create branch of a CRUD set with no explicit routing help.

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

Deploy Server