Skip to main content
Glama
Sign In
seosiri-biorobotics

seosiri-biorobotics

Official
by SEOSiri-Official
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

translate_emg_to_actuation

Translates EMG microvolt input into deterministic joint angles and velocity profiles for safe prosthetic actuation.

Instructions

Translates human muscle electrical signals (EMG in microvolts) into safe, deterministic joint angles and velocity profiles for prosthetic actuation.

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": {
      "emg_microvolts": "<emg_microvolts>"
    },
    "name": "translate_emg_to_actuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
joint_idNoelbow_servo
emg_microvoltsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions 'safe, deterministic' outputs, which adds behavioral context, but lacks details on calibration, error handling, or edge cases.

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?

Single sentence, no redundant words, front-loaded with action and resource.

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?

The tool is simple with 2 parameters and an output schema, but missing usage guidelines and full parameter semantics; adequate but not comprehensive.

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 0%, so description adds value by explaining emg_microvolts and the output (joint angles, velocity profiles). However, joint_id parameter is not explained beyond its default.

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 states the tool translates EMG signals into joint angles and velocity profiles for prosthetic actuation, using specific verbs and resources, and distinguishes it from unrelated sibling tools.

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, no prerequisites or exclusions provided; the description only implies usage for prosthetic actuation.

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