Skip to main content
Glama
Sign In
sylvia-iot-mcp

sylvia-iot-mcp

by woofdogtw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

device_delete

Delete an IoT device and all its associated resources by providing the device ID to clean up the platform.

Instructions

Delete a device and all its resources.

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": {
      "deviceId": "<deviceId>"
    },
    "name": "device_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceIdYesThe device ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it does warn that deletion removes the device and all its resources. However, it does not mention irreversibility, required permissions, or what happens to dependent records, leaving a partially complete behavioral picture.

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?

One short sentence that front-loads the action and destructive scope. Every word contributes to the meaning, and there is no filler or redundant explanation.

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?

Adequate for a one-parameter delete operation: the device ID and destructive scope are covered, and there is no output schema that needs explanation. It could be more complete by noting irreversibility and when to use single deletion versus bulk or range deletion.

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 fully documents the single parameter (deviceId with description), so the description need not add parameter details. The phrase 'a device' maps to deviceId without adding extra semantic value.

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 clear verb ('Delete'), a target resource ('a device'), and broad scope ('all its resources'), so an agent knows this removes an individual device and its associated data. It does not explicitly contrast with sibling tools like device_bulk_delete or device_range_delete, but the singular 'a device' helps differentiate it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus device_bulk_delete or device_range_delete, nor any prerequisites or conditions. Usage is only implied by the tool name and the singular phrasing.

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

Deploy Server

Other Tools