Skip to main content
Glama
Gearotons

servomotor-mcp

by Gearotons
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_to

Move a servomotor to an absolute angle in degrees and wait until it settles. Use when a target position is specified, such as 'go to 90 degrees' or 'one full turn'.

Instructions

Move one motor to an ABSOLUTE angle in degrees and wait for it to finish.

Use when the user names a target position ("go to 90 degrees", "one full turn" = 360). Angles are unbounded multi-turn (720 = two full turns). speed_dps is degrees/second (default 180). Enables the motor's MOSFETs automatically and returns the settled position. For very long moves (>30 s) prefer go_to_position plus get_n_queued_items polling so the tool call doesn't time out.

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?

No annotations are provided, so the description carries the full burden. It discloses critical behaviors: it waits for completion, enables MOSFETs automatically, returns the settled position, and notes potential timeout for long moves. It doesn't mention error handling or reaction to invalid motors, but overall meets the need for a motor-movement tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences long, front-loading the core purpose with a bold key term. The first sentence is concise and informative. The later sentences add details that are necessary (speed unit, motor identification) and alternate usage. It's slightly dense but no fluff, so a 4 is warranted.

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 the complexity (absolute multi-turn moves, timeout risk), the description covers the essentials: what it does, how parameters work, and when to use an alternative. It doesn't cover error scenarios or return format specifics, but for a motor move tool with no output schema, it's complete enough for an agent to call correctly.

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?

Schema coverage is 0%, so the description must compensate. It explains 'degrees' as absolute angle with examplesholistic, and defines 'speed_dps' with default. For 'motor', it gives a detailed semantic definition (alias number or 16-hex-digit ID) beyond the schema's generic string type. This is strong compensation for the lack of schema descriptions.

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 clearly states the verb ('move'), resource ('one motor'), and mode ('ABSOLUTE angle in degrees'), distinguishing it from relative moves by name. It also gives concrete examples ('go to 90 degrees', 'one full turn' = 360) and key semantic details like unbounded multi-turn angles. This sets it apart from siblings like move_relative and trapezoid_move.

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

Usage Guidelines5/5

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

Explicitly states when to use: when the user names a target position (absolute), contrasting with relative moves. It also provides an alternative for long moves ('go_to_position' plus 'get_n_queued_items' polling) to avoid timeouts. This is exemplary guidance for tool selection.

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