Skip to main content
Glama
Gearotons

servomotor-mcp

by Gearotons
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_communication_statistics

Retrieve and optionally reset communication error counters for a servomotor, including CRC32, packet decode, framing, overrun, noise errors, to assess RS485 link reliability.

Instructions

Get and optionally reset the CRC32 error counter [Firmware command "Get communication statistics", group: Status & Monitoring.] Parameters:

  • resetCounter: Reset flag (1 to reset the counter after reading, 0 to just read) Returns:

  • crc32ErrorCount: Number of CRC32 errors detected

  • packetDecodeErrorCount: Number of packet decode errors detected

  • firstBitErrorCount: Number of times that the first bit in the first byte of a packet was not 1 as expected

  • framingErrorCount: Number of framing errors detected during reception from the RS485 interface

  • overrunErrorCount: Number of overrun errors detected during reception from the RS485 interface

  • noiseErrorCount: Number of noise errors detected during reception from the RS485 interface motor: an alias number (e.g. 88), a 16-hex-digit unique ID (e.g. "0123456789ABCDEF"), or "all" to broadcast to every motor on the bus (broadcasts get no responses back).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
motorYes
resetCounterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the read/reset side effect, the meaning of resetCounter, and the broadcast behavior where 'all' motors return no responses. This gives the agent a clear model of what happens when the tool is invoked.

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 moderately long but every section earns its place: purpose, parameters, and return values. The return-value list is a bit verbose but necessary since there is no output schema. No filler or redundant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is self-contained for a two-parameter tool with no annotations and no output schema. It covers parameter formats, return fields, and special broadcast behavior, so an agent can call it correctly without needing external context.

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 description coverage is 0%, but the description fully compensates by explaining the resetCounter flag semantics and the accepted motor formats (alias, 16-hex-digit ID, or 'all' broadcast). This adds substantial meaning beyond the bare schema types.

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 clearly states the function: 'Get and optionally reset the CRC32 error counter', and lists the full set of communication statistics returned. It is specific about the resource (communication statistics) and differentiates itself from generic status tools, though it does not explicitly name sibling alternatives.

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?

Usage is implied through the 'Status & Monitoring' group reference and the optional reset behavior, but there is no explicit guidance about when to choose this tool versus siblings like get_motor_status or get_status, and no exclusions are stated.

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