Skip to main content
Glama
Sign In
BonengDriveMCP

BonengDriveMCP

by time32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

plan_drive_run

Preview a drive speed run without starting it, validating speed, duration, and direction to ensure safe execution.

Instructions

预览速度运行，不启动。默认上限取当前电机额定/最大转速较小值，maximum_abs_speed可降低。自动选择固定16位编码，超过327.67rpm可用百分比给定，预览给出实际量化速度和分辨率。duration_s默认null持续运行，用户未说明时先询问持续或限时；长于20秒自动后台执行，有限时长最多2147483.647秒。需电机/负载、现场停机条件及B05.01=0；不自动切换模式，不生成外部斜坡。仅用户明确允许运行中反向时设置allow_direction_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": {
      "speed": "<speed>"
    },
    "name": "plan_drive_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoCOM7
speedYes
transportNoselected_tcp
backgroundNo
duration_sNo
speed_unitNorpm
maximum_abs_speedNo
local_stop_availableNo
restore_control_modeNo
allow_direction_changeNo
motor_load_descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only mark it as non-read-only, non-destructive, non-idempotent; the description adds substantive behavior beyond that: preview-only output with quantized speed and resolution, automatic background execution past 20 s, a hard 2147483.647 s duration ceiling, and explicit non-actions (no mode switching, no ramps). A minor ambiguity remains around what 'auto background execution' means for a tool that supposedly does not start anything.

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?

Front-loaded with the purpose and the speed encoding rule, and every clause carries information with no filler. It is dense semicolon-chained prose, though, so the safety preconditions and the direction-change caveat are harder to scan than they need to be.

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 an 11-parameter planning tool with a rich output schema, the description covers purpose, speed semantics, safety preconditions, duration behavior and explicit non-actions. The remaining gap is transport/port and restore_control_mode semantics, which affect execution context rather than the plan itself.

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?

With 0% schema description coverage across 11 parameters, the description carries the load and does so for the important ones: speed unit/quantization limits (16-bit, 327.67 rpm threshold for percentage setpoints), duration_s default null plus the 20 s and max-duration rules, maximum_abs_speed as a downward clamp, and the conditional for allow_direction_change. port, transport, background and restore_control_mode are still left undocumented.

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?

States a specific verb and resource (preview a drive speed run) and immediately scopes it with '不启动' (does not start), which implicitly separates it from the sibling execute_drive_run. An agent can tell what it produces without opening the schema.

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?

Gives real routing conditions: ask the user about continuous vs. timed when duration is unspecified, requires motor/load info, on-site stop conditions and B05.01=0, and warns that it will not auto-switch mode or generate external ramps. It stops short of naming execute_drive_run as the follow-up step for actually running.

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