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

tuya-local-mcp

by meow-dot-py
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cancel_timer

Cancel a specific pending timer by ID or clear all scheduled timers at once to stop unwanted automatic Tuya device actions.

Instructions

Cancel a pending timer by id, or every pending timer with "all".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_idNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses only that "all" wipes every pending timer, without flagging that as an irreversible bulk operation. It says nothing about behavior for unknown ids, whether running timers are also stopped, whether the call is idempotent, or what result the caller receives.

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 that states the resource, the identifier mode, and the bulk mode with no filler. It could be split to surface the dangerous default, but nothing is wasted.

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 tool with zero annotations, no output schema, and a parameter that defaults to canceling everything, the definition is under-specified. An agent can invoke it, but cannot confidently predict the blast radius of omitting timer_id or what the caller gets back.

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 coverage is 0% and the single parameter has no description in the schema, so the description must compensate. It does add the crucial fact that timer_id accepts the literal "all", but it omits the most consequential detail: the schema default is "all", meaning an omitted argument cancels every timer, and this hazard is never stated.

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?

States a specific verb plus resource ("Cancel a pending timer") and distinguishes the two scopes it covers: single timer by id versus every pending timer via "all". It never names the sibling list_timers as the way to discover ids, so it stops short of full sibling differentiation.

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 to cancel a pending timer. There is no explicit guidance on when not to use it, no mention of how to obtain a timer_id (presumably list_timers), and no advice on confirming intent before the bulk "all" path.

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