Skip to main content
Glama
Sign In
tactus

tactus

by ProjectAILiberation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Linear stroke

linear

Command physical hardware to move a stroker to a specified position over a duration. Provide device ID, position (0.0-1.0), and duration in milliseconds.

Instructions

[Hardware control] Forwards a command to physical hardware. Move a stroker to a position over a duration.

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>",
      "position": "<position>",
      "duration_ms": "<duration_ms>"
    },
    "name": "linear"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYesTarget position, 0.0-1.0
device_idYesDevice id from list_devices
duration_msYesTime to reach the position, ms
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

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose side effects, safety profile, or whether the command is destructive or read-only. Minimal behavioral context beyond the basic action.

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 very short (two sentences) with no fluff, but it could be more informative without sacrificing conciseness. Slightly too terse.

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?

Adequate for the basic action, but given the presence of sibling tools with similar motions and no output schema, more context on when to use linear vs oscillate/rotate would improve completeness.

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?

Schema coverage is 100% with descriptions for all parameters, so the description adds no extra meaning. Baseline score of 3 is appropriate.

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 tool moves a stroker to a position over a duration, using specific verbs and resource. However, it does not distinguish this from siblings like oscillate or rotate, which also involve movement.

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?

No guidance on when to use this tool versus alternatives. The description lacks context on prerequisites, conflicts, or preferred scenarios.

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