sylvia-iot-mcp

device_route_bulk_delete

Bulk delete device routes for up to 1024 network addresses by specifying the application ID, network ID, and address list.

Instructions

Bulk delete device routes 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": {
      "applicationId": "<applicationId>",
      "networkId": "<networkId>",
      "networkAddrs": "<networkAddrs>"
    },
    "name": "device_route_bulk_delete"
  }
}

Input Schema

Name	Required	Description
`networkId`	Yes	The network ID of the devices.
`networkAddrs`	Yes	Network addresses to delete routes for (max 1024).
`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 conveys a destructive operation but does not state whether the deletion is permanent, whether any associated data is affected, whether authorization is required, or what the outcome/response looks like. This is a meaningful gap for a mutating bulk operation.

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, front-loaded sentence with zero filler. It communicates the core action, the target resource, the key input mechanism, and a hard constraint in one compact clause.

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?

For a destructive bulk operation with no annotations and no output schema, the description is thin. It omits important operational context such as whether the delete is permanent, whether route entries are removed from all devices in the list, and what the agent should expect after success. The schema fully covers parameters, but behavioral context is lacking.

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 networkId, networkAddrs, and applicationId. The description reinforces the 'address list' aspect and the 1024 limit, but adds little beyond the schema. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 verb ('bulk delete'), a specific resource ('device routes'), and a method ('by address list'). It clearly indicates this is the mass-deletion counterpart to device_route_delete, though it does not explicitly name the sibling tool.

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 word 'bulk' implies this is for deleting multiple device routes at once, and 'max 1024' sets a volume boundary. However, there is no explicit guidance about when to prefer this over device_route_delete or device_route_range_delete, nor any when-not-to-use conditions.

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

Deploy Server