Stop all (emergency)
stop_allInstantly halts all connected devices. Emergency stop for hardware.
Instructions
Immediately stop every connected device. Emergency stop.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
stop_allInstantly halts all connected devices. Emergency stop for hardware.
Immediately stop every connected device. Emergency stop.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears the full burden. It states the immediate action but does not disclose potential side effects (e.g., devices may need manual restart) or any prerequisite conditions.
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 only two sentences, efficiently conveying the core purpose and usage context without any filler.
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?
Given no parameters, no output schema, and no annotations, the description is mostly adequate. Additional detail about post-stop state or recovery could improve it, but for a simple emergency stop it is sufficient.
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?
There are no parameters, so the description does not need to add parameter meaning. The schema is empty and coverage is 100%, which is acceptable.
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 clearly states 'Immediately stop every connected device' and the title includes 'Emergency', making the purpose unmistakable and distinguishing it from 'stop_device' for individual devices.
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 says 'Emergency stop', which implies when to use it. It does not explicitly say when not to use it, but the context makes it clear that this is for stopping all devices in urgent situations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ProjectAILiberation/tactus'
If you have feedback or need assistance with the MCP directory API, please join our Discord server