Skip to main content
Glama
Sign In
robotarm

robotarm

by walcorg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reset

Clears a software stop after human confirmation that the robot cell is safe, enabling operation to resume.

Instructions

Clear a software stop. Only call after the human confirms the cell is safe.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reset"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the critical safety prerequisite, but it does not explain whether resetting resumes motion, clears faults or alarms, is reversible, or what operational state follows.

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 two short sentences with no filler, and the safety precondition is clearly stated after the core action. Every sentence contributes useful operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter reset tool, the definition identifies the action and the human-safety prerequisite. However, for a safety-critical operation with no annotations or output schema, it should also clarify the effect of clearing a software stop, such as whether operation resumes or faults are cleared.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there are no parameter semantics to explain. The schema covers 100% of an empty argument object, and the description correctly adds no unnecessary parameter detail.

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 and object: "Clear a software stop." This distinguishes it from the sibling stop tool by indicating it removes a stop condition rather than initiating one, though it does not explicitly name or compare against stop.

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

Usage Guidelines4/5

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

It gives a clear precondition: call only after a human confirms the cell is safe. That is useful when-to-use guidance, but it does not name alternatives or describe when not to use this tool beyond the safety confirmation.

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

Deploy Server

Other Tools