Skip to main content
Glama
clawtouch-mcp

clawtouch-mcp

by tinqiao-oss

device.status

Reports the connected board's firmware version, board name, and absolute pointer support without sending any HID input. Connects to the board first when needed.

Instructions

Ask the board what it is: firmware version, board name, whether it has the absolute pointer and whether this server uses it. Connects to the board first if it is not connected. Sends no HID report: nothing is pressed or moved.

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": "device.status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses a side effect (it will connect to the board if disconnected) and explicitly states it sends no HID report and nothing is pressed or moved, which is exactly the safety signal an agent needs. It stops short of covering latency, failure modes, or caching, so it isn't exhaustive.

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, both front-loaded and load-bearing: the first states what is returned, the second states the connection side effect and the non-mutating guarantee. No restatement of the name, no filler.

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?

Because there is no output schema, the description must enumerate return values, and it does so concretely for a zero-parameter probe, along with the implicit-connection side effect. The only gap is that it never positions itself against device.info or device.list, which matters given how similar those siblings look.

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 there is nothing for the description to disambiguate beyond what the empty schema already shows; the baseline of 4 applies. The description correctly spends no words on parameters.

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 a specific verb (query the board) and enumerates the concrete fields returned: firmware version, board name, absolute-pointer support, and whether the server uses it. It does not differentiate itself from the sibling device.info, so an agent must infer the split, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and the close sibling device.info is never mentioned as the alternative for any scenario. The only contextual note is 'Connects to the board first if it is not connected,' which is behavioral rather than routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.