Skip to main content
Glama
Sign In
BonengDriveMCP

BonengDriveMCP

by time32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_drive_runtime_status

Read-onlyIdempotent

Read drive runtime status including state machine, control/status words, and speed/current parameters without taking control or starting the motor.

Instructions

只读状态机、控制字、状态字、PC 指令和速度/电流相关参数；不会取得控制权或启动电机。

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": "read_drive_runtime_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoCOM7
transportNoselected_tcp

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is largely covered. The description reinforces that it will not acquire control or start the motor, which is useful context, but it does not add details about transport behavior, failure modes, or limits beyond the annotations.

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 a single compact sentence with the core read scope and safety constraint front-loaded. Every clause contributes useful information without repetition or filler.

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-value details need not be in the description. The description gives a good high-level picture of what is read and what is not done, but it leaves the connection parameters and sibling-tool selection unexplained.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not mention either the port or transport parameter. It therefore adds no meaning beyond the bare schema and fails to compensate for the lack of parameter documentation.

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 names the specific resources it reads: state machine, control word, status word, PC command, and speed/current-related parameters. It also clarifies that it does not take control or start the motor, which helps distinguish it from drive-control siblings, though it does not explicitly contrast with readers such as get_drive_run_status or read_drive_position_status.

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?

The read-only scope and the explicit assurance that it will not take control or start the motor imply it should be used for monitoring/inspection rather than actuation. However, it does not state when to choose this tool over related drive-status readers or control tools.

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