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

tuya-local-mcp

by meow-dot-py
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_timers

Lists pending timers created by delay_seconds or the CLI sleep command, showing each timer's ID, target action, and scheduled time.

Instructions

List pending timers (from delay_seconds or the CLI's sleep): id, what, when.

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": "list_timers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that timers come from delay_seconds or the CLI's sleep and that results include id, what, and when, but it omits explicit read-only behavior, ordering, and whether expired timers are excluded.

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 definition is a single front-loaded sentence with no filler. The parenthetical efficiently explains timer sources, and the colon cleanly introduces the returned fields.

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 simple zero-parameter list tool with no output schema or annotations, the description is nearly complete: it says what is listed, where those timers come from, and what fields are returned. Minor gaps remain around ordering, exact field types, and whether all pending timers are included.

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

Parameters4/5

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

There are zero parameters, so the baseline is 4. The mention of id, what, and when adds return-value context rather than parameter semantics.

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 gives a specific verb ('List') and resource ('pending timers'), plus the timer sources and returned fields. It is clearly distinguishable from cancel_timer and the light-related siblings by intent, though it does not explicitly route the agent to alternatives.

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: call this to see pending timers. There is no explicit when-to-use versus when-not guidance, and it does not name an alternative such as cancel_timer for acting on a timer.

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