BonengDriveMCP

Overview Schema Source Related Servers Discussions Admin

plan_drive_position_move

Preview and validate relative or absolute drive positioning moves, including speed limits, travel range, acceleration, timeout, and stop behavior before execution.

Instructions

预览相对/绝对位置运动。先建立坐标及行程范围，速度为正整数rpm并受额定/在线JOG上限约束，加减速由驱动器处理。绝对目标按参考零点计算差值；列出临时模式及JOG参数变更，停机后恢复，可能写EEPROM。allow_mode_change须用户允许。默认等待定位完成后停止释放，可设超时且随时可停止；首版要求固定方向/电子齿轮选择。

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": {
      "position": "<position>",
      "maximum_speed_rpm": "<maximum_speed_rpm>",
      "motor_load_description": "<motor_load_description>",
      "local_stop_available": "<local_stop_available>"
    },
    "name": "plan_drive_position_move"
  }
}

Input Schema

Name	Required	Default
`mode`	No	relative
`port`	No	COM7
`unit`	No	pulses
`position`	Yes
`timeout_s`	No
`transport`	No	selected_tcp
`acceleration_ms`	No
`allow_mode_change`	No
`maximum_speed_rpm`	Yes
`local_stop_available`	Yes
`motor_load_description`	Yes
`position_tolerance_pulses`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 3, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Goes well beyond the annotations: it warns that temporary mode and JOG parameter changes are listed, restored after stop, and '可能写EEPROM' (may write EEPROM) — a persistent side effect an agent must know about. It also specifies wait-for-in-position-then-release default behavior and an optional timeout. Slight tension with destructiveHint=false given the possible EEPROM write, but not a true contradiction.

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

Conciseness3/5

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

The leading preview statement is correctly front-loaded, but the body is a dense run-on chain of constraints (coordinate setup, rpm bounds, EEPROM, timeout, first-version limits) without separation. Every clause is relevant, yet the lack of structure makes it harder to scan than it needs to be.

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?

An output schema exists, so return values need no explanation, and the side-effect/permission/timeout notes are valuable. Still, for a 12-parameter motion-planning tool the description omits guidance on unit/transport selection and two required parameters, leaving the agent to guess at inputs it must supply.

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 0%, so the description carries the burden for 12 parameters. It explains mode/position (absolute computed as a delta from the reference zero), maximum_speed_rpm (positive integer rpm bounded by rated/online JOG limits), timeout_s, and allow_mode_change, but leaves port, unit, transport, position_tolerance_pulses, and the required motor_load_description and local_stop_available completely unexplained.

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?

Opens with a specific verb+resource: '预览相对/绝对位置运动' (preview relative/absolute position moves), which cleanly separates it from the sibling execute_drive_position_move. It does not name that sibling explicitly, so the preview-vs-execute routing must be inferred.

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?

Prerequisites are stated ('先建立坐标及行程范围') and a permission gate is given ('allow_mode_change须用户允许'), which implies this is the safe dry-run step. However, it never says explicitly to call this before execute_drive_position_move or instead of read_drive_motion_limits, so the when-to-use decision is only implied.

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

Deploy Server