sylvia-iot-mcp

device_route_range_delete

Remove multiple device routes at once by specifying a hex address range. Apply to a network and application to clean up routes in bulk, up to 1024 entries.

Instructions

Bulk delete device routes by hex address range (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": {
      "applicationId": "<applicationId>",
      "networkId": "<networkId>",
      "startAddr": "<startAddr>",
      "endAddr": "<endAddr>"
    },
    "name": "device_route_range_delete"
  }
}

Input Schema

Name	Required	Description
`endAddr`	Yes	End hex address, same length as startAddr.
`networkId`	Yes	The network ID of the devices.
`startAddr`	Yes	Start hex address.
`applicationId`	Yes	The application ID of the routes to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal a maximum of 1024 deletions, but it does not explain whether the range is inclusive, whether deletion is permanent, what happens when the limit is exceeded, or what response/errors to expect. For a destructive bulk operation, 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?

A single, focused sentence that front-loads the core operation and includes the key limit. Every word adds value, and there is no redundant or filler content.

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?

This is a destructive bulk operation with no annotations and no output schema, so more context is needed. The description omits boundary behavior, failure semantics, and expected effects beyond 'delete'. These are important for an agent to confidently invoke and interpret the result.

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 schema already documents each parameter. The description adds the 'hex address range' framing and the 1024 cap, which gives context to startAddr/endAddr, but it does not add substantive meaning beyond what the schema already provides.

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?

The description states a specific operation (bulk delete), a clear resource (device routes), and the method of selection (hex address range). This distinguishes it from single delete and bulk create/range create siblings, though it doesn't explicitly name any sibling.

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 'by hex address range' implies this is the right tool when deleting many routes selected by range rather than by explicit route IDs. However, the description does not explicitly say when not to use it or point to alternatives like device_route_bulk_delete, leaving some interpretation to the agent.

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

Deploy Server