sylvia-iot-mcp

application_delete

Delete an application and all its resources to free up the IoT platform. Use when you need to remove an application and its associated data entirely.

Instructions

Delete an application 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": {
      "applicationId": "<applicationId>"
    },
    "name": "application_delete"
  }
}

Input Schema

Name	Required	Description	Default
`applicationId`	Yes	The application ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A4/5.0

Behavior4/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 disclosing behavior. It clearly indicates a destructive action and, importantly, notes that deletion cascades to 'all its resources', which is a critical side effect. It does not mention reversibility or error behavior, but the core destructive trait is explicit.

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 no filler. Every word adds value, especially the resource-scope qualifier 'and all its resources'.

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 one-parameter delete operation with no output schema, the description adequately covers the input and the effect of the call, including the cascade to all resources. It could add notes on permanence or expected response, but the low complexity makes the current description sufficient for safe invocation.

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 schema already documents applicationId at 100% coverage with a clear description ('The application ID to delete'). The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 uses a clear imperative verb ('Delete') with a specific resource ('an application') and a meaningful scope qualifier ('and all its resources'). This makes the tool's function unambiguous and distinguishes it from siblings like application_update, application_get, and application_list.

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?

Usage is implied by the verb: use this tool when an application should be removed. However, the description provides no explicit guidance on prerequisites, consequences, or when not to use it, leaving the agent to infer the decision context from the tool name and sibling tools.

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

Deploy Server