Retrieve a complete list of all defined scenes within your Shelly smart home. View the name, description, and associated action count for each configured scene.
List defined scenes (name, description, action count). Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.3Input schema / additionalPropertiesAdded value: +falsev0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description's 'Read-only' simply restates that with no added behavioral context. The parenthetical field list duplicates what the output schema already exposes; no auth, rate-limit, or scope caveats are provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence plus a two-word safety tag; nothing is wasted and the essential verb+resource leads. Appropriate size for a trivial no-argument list tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be explained, and with zero parameters and full annotation coverage the description is nearly complete. It only lacks any routing hint versus its sibling scene tools, keeping it just short of 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool is 4. No parameter-level detail is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List defined scenes') and even enumerates the returned fields (name, description, action count), so the agent knows exactly what it gets. It does not explicitly differentiate itself from the closely related shelly_scene_get sibling, which is the one place an agent could pick the wrong tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or when-not-to-use guidance is given, and the obvious alternative shelly_scene_get (single-scene detail) is never named. Usage is only implied by the name and purpose, which is the definition of a 3.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.