Lists all SimpliSafe systems on your account, showing alarm state, alarming status, connectivity, and power. Use this to obtain the system ID (sid) for other tools.
List the SimpliSafe systems on this account with their current alarm state (off/home/away), alarming status, connectivity and power status. Start here to get the sid other tools take.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates that this is a read-only operation, and the description is consistent with that. It adds useful behavioral context by describing what data is returned, including alarm state values and connectivity/power status, and it explains that the returned sid is needed by other tools. This goes beyond the annotation without contradicting it.
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?
The description is two sentences with no filler. It front-loads the action and resource, then adds only essential guidance about the sid. Every sentence earns its place.
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?
For a parameterless list tool with no output schema, the description fully covers what the tool does, what fields are returned, and how the result is used by sibling tools. There is no critical missing context.
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 has zero parameters, so the schema carries no parameter burden. The description correctly notes that the tool lists systems for the account and provides the sid for downstream tools, which is the only meaningful semantic context needed here.
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?
The description states a specific verb and resource: 'List the SimpliSafe systems on this account.' It also names the key output fields (alarm state, alarming status, connectivity, power status), making the tool's purpose immediately clear. The closing 'Start here' helps distinguish it as the entry point from sibling tools that require an sid.
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?
The description explicitly tells the agent to 'Start here to get the sid other tools take,' which is strong contextual guidance for when to call this tool before others. It does not provide explicit exclusions or alternatives, but the entry-point role is clearly communicated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.