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

m8-tracker-mcp

by cocopon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Press M8 buttons

press_buttons

Press one or more Dirtywave M8 buttons simultaneously, including modifier combinations, for a set duration and repeat count to control the device over USB.

Instructions

Press one or more M8 buttons simultaneously for a short duration (default 50ms), then release, optionally several times. Use arrays to combine modifier-style inputs; names match the M8 hardware labels. E.g. ["shift","right"] for SHIFT+RIGHT (move to the next screen), ["edit","up"] with repeat 3 to raise a hex value by 0x30.

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": {
      "buttons": "<buttons>"
    },
    "name": "press_buttons"
  }
}

Input Schema

NameRequiredDescriptionDefault
repeatNo
buttonsYesButtons to press simultaneously
duration_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the press-then-release model, the 50ms default, and optional repetition. It omits prerequisites (must the device be connected first, e.g. via connect?) and says nothing about behavior on failure or whether presses queue/block.

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?

Front-loaded with the core action, then usage examples — every sentence adds either behavior or a concrete invocation. No filler or restatement of the title.

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 3-parameter, no-output-schema tool, this covers what to send and what it does well enough to call correctly. The one real gap is the missing connection prerequisite linking it to the 'connect' sibling.

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?

Schema coverage is only 33% (only 'buttons' is described), but the description compensates by explaining duration's default of 50ms and repeat's semantics with a concrete example ('repeat 3 to raise a hex value by 0x30'). The enum values themselves are never enumerated in text, but the examples convey the label space adequately.

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 concrete verb ('Press') and resource ('M8 buttons') with the simultaneity scope spelled out, which implicitly separates it from press_sequence and press_note. It never names those siblings explicitly, so the differentiation is inferred rather than declared.

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?

Two worked examples effectively define when to use it: array combos for modifier-style inputs, and repeat for repeated increments like raising a hex value by 0x30. There is no explicit exclusion or routing to press_sequence/press_note when a multi-step or note-entry action is needed.

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