Skip to main content
Glama

RTK Motion — Motion Capture, Biomechanics, Threat & Fleet Intelligence

by io.rtkmotion
OverviewDiscussionsAdmin

get_robotarget

Multi-robot joint trajectories (NPZ) for sim_to_real_retargeting or imitation_learning. Platforms: Unitree G1 (43 DOF: 29 body + 14 hand), Unitree H1 (19 DOF), Apptronik Apollo (32 DOF) — specify via robot= param. MoveIt/ROS and Isaac Sim compatible, 60 fps, latency <500ms. Pay $15 USDC on Base (chain 8453, USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to RTK wallet 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C; pass tx hash as payment_tx. Eth/Solana: /.well-known/x402. Cheaper $0.25 trial sample: call get_trial_robotarget.

Input Schema

NameRequiredDescriptionDefault
robotNoTarget robot platform: 'g1' (Unitree, 43 DOF = 29 body + 14 hand), 'h1' (Unitree, 19 DOF), or 'apollo' (Apptronik, 32 DOF). Defaults to 'g1'. Future platforms appear in the lesson's files.robotarget.robots list.
subjectYesSubject name (e.g. 'subject_1' or 'subject_2')
quote_idNoRedeem this item from a negotiated quote you already paid with pay_quote (q_...). Use instead of payment_tx / x_payment: no further payment is taken.
x_paymentNoPreferred (x402 exact / gasless): base64 X-PAYMENT payload — a signed EIP-3009 transferWithAuthorization for this tool's USDC price to our wallet. Redeemable only by its signer; no gas needed.
payment_txNoUSDC transaction hash. Send $15 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here.
lesson_pathNoLesson path, e.g. 'BJJ/Training/KimuraFromSideControl/Lesson001'. Defaults to first available lesson.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / quote_id
      Added value: +{
+  "description": "Redeem this item from a negotiated quote you already paid with pay_quote (q_...). Use instead of payment_tx / x_payment: no further payment is taken.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / robot / description
      Previous value: -"Target robot platform: 'g1' (Unitree, 24 DOF) or 'h1' (Unitree, 19 DOF). Defaults to 'g1'. Future platforms appear in the lesson's files.robotarget.robots list."New value: +"Target robot platform: 'g1' (Unitree, 43 DOF = 29 body + 14 hand), 'h1' (Unitree, 19 DOF), or 'apollo' (Apptronik, 32 DOF). Defaults to 'g1'. Future platforms appear in the lesson's files.robotarget.robots list."
  3. Changed1 schema field changed
    • addedInput schema / properties / x_payment
      Added value: +{
+  "description": "Preferred (x402 exact / gasless): base64 X-PAYMENT payload — a signed EIP-3009 transferWithAuthorization for this tool's USDC price to our wallet. Redeemable only by its signer; no gas needed.",
+  "type": "string"
+}
  4. Changed2 schema fields changed
    • changedInput schema / properties / payment_tx / description
      Previous value: -"Transaction hash proving payment of $15 USD to the RTK wallet"New value: +"USDC transaction hash. Send $15 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here."
    • changedInput schema / properties / robot / description
      Previous value: -"Target robot platform (e.g. 'g1'). Defaults to 'g1'. Must be one of the platforms listed in the lesson's files.robotarget.robots."New value: +"Target robot platform: 'g1' (Unitree, 24 DOF) or 'h1' (Unitree, 19 DOF). Defaults to 'g1'. Future platforms appear in the lesson's files.robotarget.robots list."
  5. Changed1 schema field changed
    • addedInput schema / properties / robot
      Added value: +{
+  "description": "Target robot platform (e.g. 'g1'). Defaults to 'g1'. Must be one of the platforms listed in the lesson's files.robotarget.robots.",
+  "type": "string"
+}
  6. Changed3 schema fields changed
    • removedInput schema / properties / competitor
      Removed value: -{
-  "description": "Competitor name (e.g. 'Professor' or 'Student')",
-  "type": "string"
-}
    • addedInput schema / properties / subject
      Added value: +{
+  "description": "Subject name (e.g. 'subject_1' or 'subject_2')",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "competitor"
-]New value: +[
+  "subject"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / competitor / description
      Previous value: -"Competitor name (e.g. 'Boca' or 'Thane')"New value: +"Competitor name (e.g. 'Professor' or 'Student')"
  8. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses output format (NPZ), compatibility (MoveIt/ROS, Isaac Sim), frame rate, latency, and the payment flow including Base USDC and x402 alternatives. It still omits error/refund behavior and file-size or delivery details, so it is strong but not exhaustive.

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 dense and front-loads the resource and platforms before payment instructions. Most sentences earn their place, though the Ethereum/Solana pointer and repeated payment details add slight clutter.

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 paid, multi-parameter retrieval tool with no output schema, the description covers the essential output format, compatibility, latency, platform options, and payment workflow. It is nearly complete, with only minor gaps around file contents and failure handling.

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 description coverage is 100%, so parameter meanings are already well documented. The description reinforces the robot and payment_tx parameters but adds little semantic detail beyond the schema, making the baseline 3 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 identifies the resource as multi-robot joint trajectories in NPZ format and gives concrete use cases (sim_to_real_retargeting, imitation_learning). It also distinguishes the full tool from the cheaper get_trial_robotarget sibling, though it does not use an explicit retrieval verb.

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?

It names appropriate use cases and explicitly points to get_trial_robotarget for a cheaper $0.25 trial sample. It does not fully articulate when the full paid tool is required versus when the trial is sufficient, leaving some inference to the agent.

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

All RTK Motion — Motion Capture, Biomechanics, Threat & Fleet Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources