sylvia-iot-mcp

device_range_create

Create multiple IoT devices at once by specifying a hexadecimal address range. Supports up to 1024 devices per batch, requiring equal-length start and end addresses.

Instructions

Bulk create devices by hex address range (max 1024). startAddr and endAddr must be same-length hex strings.

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": {
      "unitId": "<unitId>",
      "networkId": "<networkId>",
      "startAddr": "<startAddr>",
      "endAddr": "<endAddr>"
    },
    "name": "device_range_create"
  }
}

Input Schema

Name	Required	Description
`unitId`	Yes	Associated unit ID.
`endAddr`	Yes	End hex address (e.g. "800013ff"), same length as startAddr.
`profile`	No	Device profile.
`networkId`	Yes	Associated network ID.
`startAddr`	Yes	Start hex address (e.g. "80001000").

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.7/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 behavioral burden. It does disclose the 1024-device limit and the same-length hex requirement, which are genuinely useful call-preconditions. It does not disclose conflict handling (existing addresses in the range), atomicity of partial failure, or endpoint inclusivity, which matter for a bulk mutation.

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 short sentences with zero filler: the first front-loads the core purpose and limit, the second states the critical format precondition. Every clause earns its place.

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?

For a 5-parameter bulk mutation with no output schema and no annotations, the description covers purpose and key constraints but omits several things an agent needs: the shape of the response, behavior when addresses in the range already exist, and whether the range endpoints are inclusive. It is adequate but leaves meaningful gaps.

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 100%, so the baseline is 3 and the schema already documents all five parameters with examples. The description reinforces the same-length constraint and relates the 1024 cap to the startAddr/endAddr span, but adds little beyond the schema.

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?

The description names a specific verb ('create'), resource ('devices'), and mechanism ('by hex address range'), and adds the 1024-device cap. This clearly differentiates it from sibling tools like device_create (single) and device_range_delete (delete). The purpose is unambiguous on its own.

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?

The intended use is implied: call this when you need to bulk-create devices across a contiguous hex address range. However, it never explicitly contrasts with device_bulk_create or device_create, nor states when those would be preferred. The max-1024 limit is a capacity constraint rather than routing guidance.

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

Deploy Server