sylvia-iot-mcp

device_route_bulk_create

Create multiple device routes at once by providing an application ID, network ID, and a list of up to 1024 network addresses; existing routes are skipped automatically.

Instructions

Bulk create device routes by address list (max 1024). Existing routes are skipped.

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_create"
  }
}

Input Schema

Name	Required	Description
`networkId`	Yes	The network ID of the devices.
`networkAddrs`	Yes	Network addresses to create routes for (max 1024).
`applicationId`	Yes	The application ID to route devices to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/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 disclose one useful trait: 'Existing routes are skipped,' which signals idempotent behavior. However, it does not cover what happens on partial failure, whether the operation is atomic, what response to expect, or how exceeding the max of 1024 addresses is handled.

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 two short sentences with no filler. The action and key constraint are front-loaded, and the additional behavioral detail about existing routes is concise and relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a bulk create operation with three required parameters that are fully documented in the schema, the description provides the core purpose, input mode, limit, and skip behavior. Minor gaps remain around failure semantics and return values, but the description is reasonably complete for an agent to invoke the tool correctly.

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?

The input schema already documents all three parameters with descriptions, so the schema coverage is 100%. The description does not add meaning beyond the schema, aside from restating the 1024 max for the address list, which is already present in 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 verb and resource ('Bulk create device routes') and clarifies the input method ('by address list'), with a concrete limit of 1024. This clearly distinguishes it from sibling tools like device_route_create (singular) and device_route_range_create (range-based).

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 create' implies this is for creating multiple device routes at once, but the description does not explicitly contrast it with alternatives like device_route_create or device_route_range_create. There is no when-to-use/when-not-to-use guidance beyond the word 'Bulk' and the address-list input.

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

Deploy Server