SprutHub MCP Server

Overview Schema Source Related Servers Discussions Admin

sprut_set_characteristic

Set any characteristic on a SprutHub accessory—brightness, temperature, mode—by specifying accessory, service, characteristic IDs and target value.

Instructions

Set any characteristic on an accessory (brightness, temperature, mode, etc.).

Args: accessory_id: The ID of the accessory. service_id: The ID of the service (sId). characteristic_id: The ID of the characteristic (cId). value: The target value to set (boolean, integer, float, or string).

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": {
      "accessory_id": "<accessory_id>",
      "service_id": "<service_id>",
      "characteristic_id": "<characteristic_id>",
      "value": "<value>"
    },
    "name": "sprut_set_characteristic"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`service_id`	Yes
`accessory_id`	Yes
`characteristic_id`	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.9/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 burden of behavioral disclosure. It never states whether this requires specific permissions, whether the change is reversible, what happens on an invalid characteristic, or what confirmation/error is returned. Only the accepted value types are surfaced, which is thin for a mutation tool.

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?

Front-loads the purpose in one sentence followed by an Args block that mirrors the required parameters. The structure is clean and each element is relevant, though the Args list is somewhat boilerplate.

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?

An output schema exists so return values need not be described. However, for a no-annotation mutation tool with a generic sibling, the definition omits usage routing and behavioral expectations, leaving it only partially complete.

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?

Schema description coverage is 0%, so the description must compensate, and it does document all four parameters including the helpful sId/cId hints. However, the descriptions are shallow: value format, valid ranges, and how to obtain accessory/service/characteristic IDs are not explained.

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 (set) and resource (any characteristic on an accessory) with concrete examples like brightness, temperature, and mode. It does not distinguish itself from the sibling sprut_set_switch, which is likely a specialized setter for the same domain.

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 when-to-use guidance, prerequisites, or alternatives are given. The sibling sprut_set_switch is an obvious alternative for switch-type characteristics, yet the description never explains when to prefer this generic setter over it or what IDs must be resolved first.

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

Deploy Server