Skip to main content
Glama

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

by io.rtkmotion

get_spotter_cv_sample

TRIAL — a 10-crop slice of the geo-stripped commercial-truck detection corpus, to evaluate crop + de-identification quality before the full corpus (get_spotter_cv, $50). The corpus sells on verified truck crops; FMCSA-public usdot/carrier are resolved on only 90 of 1877 crops (4.8%) and this fixed trial slice lands in the unlabeled majority, so expect usdot/carrier to be null here — judge the IMAGES, not the identity fields. Returns 10 label rows + time-limited signed URLs to those 10 de-identified crops (faces/persons + non-subject text + burned-in GPS blurred). Pay $0.25 USDC on Base (chain 8453, USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to RTK wallet 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C; pass tx hash as payment_tx. Eth/Solana: /.well-known/x402. Free preview: get_spotter_cv_profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 $0.25 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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. Added

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries full behavioral burden and does so exceptionally. It discloses the return payload (10 label rows + time-limited signed URLs), the de-identification applied (faces/persons + non-subject text + GPS blur), and the key caveat that identity fields will likely be null in this slice (4.8% match rate). Payment behavior and price are also fully stated.

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 a dense paragraph with multiple clauses, but it is well-organized and front-loaded with the key 'TRIAL' identifier. The extra detail on corpus match percentages is somewhat verbose but serves to set expectations about null identity fields. Every major element (purpose, return format, payment, alternative) is present, though slightly more compact phrasing would earn a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must explain return values, and it does: 'Returns 10 label rows + time-limited signed URLs to those 10 de-identified crops.' The tool's payment complexity and trial nature are fully covered, including the unlabeled-majority caveat and free-preview path. The context is complete for an agent to decide whether to invoke this tool and how to invoke it.

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%, so the baseline is 3. The description adds meaningful context beyond the schema by naming the exact payment amount, chain, token address, and wallet, and by explaining that payment_tx is passed after sending USDC while x_payment is the preferred gasless option. This goes beyond the schema's terse field descriptions, though the schema already covers the basic parameters well.

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 opens with 'TRIAL' and clearly identifies the tool as a 10-crop sample of a geo-stripped truck detection corpus, explicitly distinguishing it from the full corpus (get_spotter_cv) and the free preview (get_spotter_cv_profile). The verb+resource+scope are specific and no ambiguity remains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this trial 'to evaluate crop + de-identification quality before the full corpus' and points to get_spotter_cv for the full corpus and get_spotter_cv_profile for a free preview. It also gives payment instructions and alternative x402 paths, making the when-to-use and alternatives clear.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools are clearly separated by domain and tier (profile/sample/full), but get_mocap_sample and get_trial_bvh both return 5-second BVH samples and could be misselected. The rehab sample/profile tools are also close in evaluation purpose, though descriptions do help distinguish them.

Naming Consistency5/5

The data-access tools consistently follow get_<domain>_<variant>, and the only navigation tools are browse_catalog and search_catalog, which also use a predictable verb_noun pattern. There is no mixing of naming styles or inconsistent verb forms.

Tool Count3/5

With 21 tools, the set is borderline heavy for a data marketplace, especially since many tools are trial/sample/profile variants of the same paid products. The broad multi-domain scope justifies some size, but several variants could be consolidated without much loss of clarity.

Completeness4/5

The tools cover catalog browsing/searching, free profiles and samples, and paid full products across motion capture, rehab biomechanics, and threat/fleet intelligence. Minor gaps exist, such as no video trial and no generic fetch-any-catalog-item tool, but agents can work around these with the existing sample tools.

Resources