sylvia-iot-mcp

device_bulk_delete

Bulk delete devices by providing a list of network addresses (max 1024) tied to a specific unit and network.

Instructions

Bulk delete devices by address list (max 1024).

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>",
      "networkAddrs": "<networkAddrs>"
    },
    "name": "device_bulk_delete"
  }
}

Input Schema

Name	Required	Description
`unitId`	Yes	Associated unit ID.
`networkId`	Yes	Associated network ID.
`networkAddrs`	Yes	Network addresses to delete (max 1024).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.5/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 for behavioral disclosure. It identifies that devices are deleted, but it does not state that deletion is irreversible, what permissions are required, whether associated routes or configuration are removed, or what the response indicates. For a destructive tool, this is a meaningful gap.

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?

The description is a single sentence with no filler; the core action, target resource, input method, and limit are all conveyed efficiently. The key information is front-loaded and easy to scan.

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 destructive bulk operation, the description omits irreversibility, permission requirements, and the result/return behavior, and there is no output schema to fill that gap. However, the schema fully documents all inputs and the purpose and limit are clearly stated, making the definition minimally viable rather than seriously incomplete.

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%, with all three parameters (unitId, networkId, networkAddrs) already documented. The description only repeats the max-1024 constraint that appears in the schema, so it adds no significant semantic value 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 states a specific operation ('Bulk delete'), a resource ('devices'), and a selection criterion ('by address list'), with the 1024-item limit. This clearly differentiates it from single-device deletion and range-based deletion among the sibling tools.

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 phrase 'bulk delete by address list' implies the tool is for deleting multiple specific devices by their addresses, and the max-1024 note sets a capacity boundary. However, it does not explicitly say when to choose this over device_delete or device_range_delete, nor what happens if the list exceeds the limit.

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

Deploy Server