Skip to main content
Glama

stop_robot

Emergency stop a robot by providing its ID to ensure safety during critical situations.

Instructions

Emergency stop a robot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
robot_idYesID of the robot to stop

Implementation Reference

  • The `stopRobot` handler method processes the tool request by sending an emergency stop command to the backend API.
    async stopRobot(args) {
      const response = await axios.post(
        `${API_BASE}/api-safety.php`,
        {
          action: 'emergency_stop',
          robot_id: args.robot_id,
        },
        { headers: { 'X-API-Key': API_KEY } }
      );
      
      return {
        content: [
          {
            type: 'text',
            text: `Robot ${args.robot_id} stopped successfully`,
          },
        ],
      };
    }
  • server.js:84-96 (registration)
    Definition of the `stop_robot` tool in the `ListToolsRequestSchema` handler.
      name: 'stop_robot',
      description: 'Emergency stop a robot',
      inputSchema: {
        type: 'object',
        properties: {
          robot_id: {
            type: 'string',
            description: 'ID of the robot to stop',
          },
        },
        required: ['robot_id'],
      },
    },
  • Request handler dispatch logic for the `stop_robot` tool.
    case 'stop_robot':
      return await this.stopRobot(args);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It implies a destructive action ('stop') but doesn't clarify critical aspects like whether this is irreversible, requires specific permissions, has safety implications, or what happens post-stop (e.g., robot state). The term 'Emergency' hints at urgency but lacks operational details.

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 description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for a simple tool.

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?

Given the tool's potential complexity (emergency stop implies safety-critical operations) and lack of annotations or output schema, the description is insufficient. It doesn't address behavioral risks, response format, or error conditions, leaving significant gaps for an agent to use it safely and effectively.

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 description coverage is 100%, with the single parameter 'robot_id' documented in the schema. The description adds no additional parameter semantics beyond implying the tool acts on a robot, which is already clear from the schema. This meets the baseline for high schema coverage.

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 clearly states the action ('Emergency stop') and target resource ('a robot'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'execute_robot_task' or 'get_robot_status', but the verb 'stop' is specific enough to convey the core function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, conditions for emergency use, or contrast with other robot-related tools like 'execute_robot_task' or 'get_robot_status', leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RedCiprianPater/mcp-server-robotics'

If you have feedback or need assistance with the MCP directory API, please join our Discord server