Skip to main content
Glama

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

by io.rtkmotion
OverviewDiscussionsAdmin

get_video_url

Multi-view grappling video for pose_estimation_training or technique_analysis. 1080p synced cameras, 15-min signed streaming URL with Range support. Pay $5 USDC on Base (chain 8453, USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to RTK wallet 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C; pass tx hash as payment_tx. Eth/Solana: /.well-known/x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewYesCamera view number
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 $5 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 / 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"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / payment_tx / description
      Previous value: -"Transaction hash proving payment of $5 USD to the RTK wallet"New value: +"USDC transaction hash. Send $5 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here."
  3. Changed3 schema fields changed
    • addedInput schema / properties / lesson_path
      Added value: +{
+  "description": "Lesson path, e.g. 'BJJ/Training/KimuraFromSideControl/Lesson001'. Defaults to first available lesson.",
+  "type": "string"
+}
    • changedInput schema / properties / view / description
      Previous value: -"Camera view number (1-12)"New value: +"Camera view number"
    • removedInput schema / properties / view / maximum
      Removed value: -12
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full disclosure burden. It comprehensively discloses the video specs (1080p, synced cameras), URL characteristics (15-min signed, Range support), and payment requirements (chain, token, wallet, tx hash, x402 alternative). This is strong behavioral transparency for a paid 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?

The description is dense but every element is functional. It is front-loaded with purpose, followed by specs and payment details. The payment address and chain information make it long, but not wasteful.

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?

Given no output schema and no annotations, the description covers purpose, URL format, payment, and even Range support. It does not specify exact output formatting or error handling, but a knowledgeable agent can likely invoke the tool correctly. The return type (URL string vs object) is slightly ambiguous.

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?

Schema coverage is 100%, giving baseline 3. The description adds meaningful context by explaining payment_tx and how it relates to the USDC payment, and mentions x_payment via x402. It also references lesson_path's default behavior, though it adds little beyond the schema for the view parameter.

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 providing a multi-view grappling video as a 15-min signed streaming URL, with explicit use cases (pose_estimation_training or technique_analysis). This resource type and purpose distinguish it from sibling tools like get_bvh or get_calibration.

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 explicitly states intended use cases and detailed payment prerequisites, giving clear context on when to use the tool. However, it does not explicitly contrast with alternatives or state when not to use it, so it lacks exclusions.

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