Skip to main content
Glama

restart_node

Restarts a specified software node on a robot to clear faults caused by that node, helping restore normal operation.

Instructions

Restart one software node on a robot. Clears a fault caused by that node.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "robot_id": "<robot_id>",
      "node": "<node>"
    },
    "name": "restart_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so safety framing is partly covered. The description adds that the operation is scoped to a single node and that a fault is cleared, but says nothing about transient downtime for that node, whether the robot must be idle, or whether dependent nodes are affected.

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?

Two short sentences, zero filler, with the action and its effect front-loaded. Nothing could be removed without losing information.

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 two-parameter mutation tool with no output schema and annotations that already carry the safety profile, the description is nearly sufficient. The remaining gap is post-call behavior, such as whether the node returns to a running state or what indication of success is returned, which the missing output schema pushes back onto the description.

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 coverage is 50%: robot_id is documented in the schema, while the node enum lists five valid values with no explanation of what each node does. The description contributes only the notion that exactly one node is restarted; it does not explain the node choices or their consequences, so it neither compensates for nor worsens the coverage gap.

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 plus resource ('Restart one software node') and states the scope ('one', 'on a robot'), which distinguishes it from fleet-level siblings like emergency_stop or get_robot_state. It stops short of naming a sibling it is commonly confused with, so the differentiation is implicit rather than explicit.

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?

'Clears a fault caused by that node' implies the trigger condition: use it when a single node is faulted. It does not state when not to use it, nor point to diagnostic alternatives like read_diagnostics to confirm which node is at fault, so the agent must infer the workflow.

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