Skip to main content
Glama
Sign In
tuya-local-mcp

tuya-local-mcp

by meow-dot-py
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_preset

Deletes a saved lighting preset by name from presets.json so it can no longer be selected or applied.

Instructions

Delete a preset from presets.json.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether deletion is permanent, whether the file is rewritten immediately, whether it errors on a missing name, or what is returned. The only behavioral hint is that the preset lives in presets.json.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is appropriately sized for the action. It is concise to the point of under-specification, but there is no wasted wording.

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 mutation with no annotations, no output schema, and no parameter documentation, so the description is the only source of behavioral information and it provides essentially none. For a delete operation an agent needs to know about irreversibility and failure modes, and both are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the single parameter "name" is documented nowhere except by its bare title. The description never explains that name must be an existing preset identifier or whether it is case-sensitive or exact-match, so the agent gets no help on the one input it must supply.

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 uses a specific verb and resource ("Delete a preset") and even names the underlying store (presets.json), so the action is unambiguous. However, it does nothing to distinguish this from its siblings get_presets and upsert_preset beyond the verb, so it stops short of a 5.

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 rather than upsert_preset, and no mention of preconditions such as the preset having to exist. The agent is left to infer that this is the removal counterpart of upsert_preset.

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