Skip to main content
Glama
Sign In
tactus

tactus

by ProjectAILiberation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rotate

rotate

Set rotation speed and direction on a hardware device. Accepts speed 0.0-1.0 and optional clockwise direction.

Instructions

[Hardware control] Forwards a command to physical hardware. Set rotation speed (and direction) on a device.

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": {
      "device_id": "<device_id>",
      "speed": "<speed>"
    },
    "name": "rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYesRotation speed, 0.0-1.0
clockwiseNoDirection; honored only if the device supports it
device_idYesDevice id from list_devices
actuator_indexNoRestrict to one actuator index; omit to drive all matching actuators

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, and the description only states it forwards a command to hardware without disclosing side effects, safety implications, or impact on device state, which is insufficient for a hardware control tool.

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?

Two concise sentences, but the first sentence is redundant ('forwards a command to physical hardware') and could be removed to improve clarity.

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?

Schema covers all parameters, but missing output schema and annotations; description lacks details on error handling, state changes, or prerequisites for a hardware operation.

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

Parameters3/5

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

The description adds minimal value beyond the 100% schema coverage; it repeats 'speed and direction' without deeper context like default behavior or interaction with actuator_index.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as hardware control for rotation, specifying speed and direction, which distinguishes it from sibling tools like vibrate or oscillate.

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 description implies use when rotating a device but lacks explicit guidance on when to use alternatives (e.g., oscillate for back-and-forth motion) or prerequisites like device connection.

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