Skip to main content
Glama
Gearotons

servomotor-mcp

by Gearotons
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_relative

Moves a servomotor incrementally by a specified number of degrees, positive or negative, and waits until it finishes. Use it to jog a bit, back off, or adjust position by a relative amount.

Instructions

Move one motor by a RELATIVE amount in degrees (+/-) and wait for it to finish.

Use for "turn a bit more", "back off 10 degrees", or incremental jogging. Any magnitude is allowed, including multiple full turns. speed_dps is degrees/second (default 180). Enables the MOSFETs automatically and returns the settled position.

motor: an alias number (e.g. 88) or a 16-hex-digit unique ID from list_motors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
motorYes
degreesYes
speed_dpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedInput schema / properties / speed
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Speed"
-}
    • addedInput schema / properties / speed_dps
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Speed Dps"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that the call waits for completion, enables MOSFETs automatically, returns the settled position, and allows arbitrary magnitude including multiple turns. This covers the most important side effects, though it omits error behavior or interactions with limits.

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?

Every sentence contributes: one verb statement, a use-case line, a speed note, a MOSFET side-effect note, and a parameter explanation. It is front-loaded with the core purpose and avoids filler.

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?

Given no output schema and no annotations, the description conveys what the tool does, when to use it, how parameters are interpreted, and that it blocks until finish and returns a position. It does not discuss error cases, but that is a minor gap for a simple relative move command.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates: it explains 'motor' can be an alias or 16-hex ID from list_motors, defines 'degrees' as relative signed degrees, and defines speed_dps with units and default. This is exactly the semantic context an agent needs beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise action: moving one motor by a relative amount in degrees and waiting for completion. It clearly distinguishes this from absolute moves and other motor operations by emphasizing 'RELATIVE' and 'incremental jogging,' making it easy for an agent to differentiate from siblings like move_to.

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?

The description explicitly lists use cases ('turn a bit more', 'back off 10 degrees', incremental jogging), which tells the agent when to use this function. It does not explicitly contrast with sibling tools, but the relative/absolute distinction and the examples provide strong guidance.

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