Skip to main content
Glama

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

by io.rtkmotion
OverviewDiscussionsAdmin

get_spotter_cv

Geo-stripped commercial-truck image corpus for detection_or_ocr_model_training. 1877 de-identified crops, every one a verified truck (equipment=truck on all 1877). FMCSA-public identity labels (usdot + carrier) are resolved on 90 crops (4.8%) and null on the rest — treat them as a bonus, not the basis of the corpus. Returns labels (JSONL, one row per crop — no plate read, no geo, no timestamp) plus time-limited signed URLs to the de-identified truck crops (faces/persons + non-subject text + burned-in GPS blurred, and EVERY plate blurred including the subject truck's own; only painted carrier markings remain). Pay $50 USDC on Base (chain 8453, USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to RTK wallet 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C; pass tx hash as payment_tx. Eth/Solana: /.well-known/x402. Images are paged — use offset to page through the corpus with the same payment_tx.

Input Schema

NameRequiredDescriptionDefault
limitNoMax image URLs to return per call (default 500).
offsetNoImage offset for paging through the corpus (default 0).
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 $50 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here.

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
    • 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"
+}
  3. 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 full burden and does well: it discloses exact privacy transforms (faces/persons, non-subject text, burned-in GPS blurred; every plate blurred including the subject truck's own), that payments are time-limited signed URLs, that 95.2% of identity labels are null, and that x_payment is the preferred gasless x402 path. Gaps: URL expiry duration is only called 'time-limited', and no failure behavior (wrong amount, reused tx) is described.

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?

Dense but front-loaded: corpus identity and composition first, then label caveat, then return payload, then payment, then paging. Every sentence carries information an agent needs to call it correctly; the long hex addresses are necessary, not filler.

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?

No output schema exists, so the description must explain returns — and it does (JSONL one row per crop with no plate/geo/timestamp, plus signed image URLs). Pricing, currency, chain, wallet and paging are all specified. Still missing signed-URL lifetime and the actual label fields, which matter for a paid bulk dataset.

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 baseline is 3, but the description adds cross-call semantics not present in the schema — that offset paging reuses the same payment_tx rather than paying again, and that the tx must be $50 USDC on chain 8453 to a specific wallet. It also frames the alt-currency path via /.well-known/x402.

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?

States a specific verb/resource: returns a geo-stripped commercial-truck image corpus (1877 verified truck crops) with labels plus signed crop URLs. It is clearly distinguishable from catalog/bundle siblings, but it never names its closest siblings (get_spotter_cv_sample, get_spotter_cv_profile, get_spotter_carrier) so the boundary is inferred rather than stated.

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

Usage Guidelines3/5

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

Gives substantive operational guidance — pay $50 USDC on Base, then page with offset and the same payment_tx, and treat identity labels as a bonus. However, it never says when to pick this full corpus over the sample/profile siblings, so selection against alternatives is left implicit.

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