Skip to main content
Glama
Sign In
m8-tracker-mcp

m8-tracker-mcp

by cocopon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Disconnect from M8

disconnect

Close the USB serial connection to the M8 so other apps like m8c or TyUploader can use it. The next tool call reconnects automatically.

Instructions

Close the USB serial connection so other apps (m8c, TyUploader for firmware updates, etc.) can use the M8. The next M8 tool call reconnects automatically.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 — and it discloses the critical behavioral trait that the connection is re-established on the next M8 tool call, which is exactly the context an agent needs before calling. It omits edge behavior such as what happens if no connection is open.

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?

Two sentences, front-loaded with the action and followed by the rationale/side effect. Nothing is wasted or repeated.

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 a no-parameter, no-output-schema lifecycle tool, the description covers purpose, motivation, and the reconnect side effect. Only minor edge-case behavior (error when already disconnected) is left unstated.

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?

The tool takes zero parameters, so the baseline is 4. The description appropriately focuses on effect rather than inputs.

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?

States a specific action and resource: "Close the USB serial connection." It is clearly the inverse of the connect sibling, though it doesn't name connect explicitly. An agent can still tell exactly what this does without ambiguity.

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 concrete conditions for use: other apps (m8c, TyUploader for firmware updates) need the port. It also pre-empts the main hesitation by noting the next M8 tool call reconnects automatically, though it doesn't say when *not* to call it.

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