Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_switch_set

Set a switch value such as a relay state or slider position between 0.0 (OFF) and 1.0 (ON) using the switch index.

Instructions

Set a switch value (e.g. relay state or slider value).

switch_index: Index of the switch. Must be >= 0. value: Target state (0.0 for OFF, 1.0 for ON, or intermediate value for sliders).

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": {
      "switch_index": "<switch_index>",
      "value": "<value>"
    },
    "name": "nina_switch_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
switch_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Discloses valid ranges for parameters (switch_index >= 0, value 0.0/1.0/intermediate). However, no mention of side effects, error handling, or prerequisites like device connection.

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?

Two efficient sentences; first states purpose, second lists parameters with constraints. No wasted words.

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?

Adequate for a simple setter, but lacks description of return values, success/failure indicators, or additional behavioral context.

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

Parameters5/5

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

Adds full meaning beyond schema (0% coverage): switch_index must be >= 0, value is OFF/ON/slider intermediate. Completely explains both parameters.

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?

Description clearly states the verb 'Set' and resource 'switch value', with specific examples (relay state or slider value). Distinguishes from siblings like nina_switch_info by indicating a write operation.

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 guidance on when to use this tool vs alternatives, such as nina_switch_info for reading. No when-not or prerequisites mentioned.

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