Skip to main content
Glama

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

by io.rtkmotion
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
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 $0.25 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

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does: it discloses de-identification scope (faces/persons, non-subject text, burned-in GPS blurred), that URLs are time-limited signed URLs, the exact payment amount/chain/token/wallet, an alternate Eth/Solana endpoint, and the 4.8% label-availability caveat. This is unusually rich behavioral context 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?

Front-loads the core purpose and the price/alternative framing before the payment mechanics, and almost every sentence earns its place. It is long and repeats USDC/wallet details already in the schema, which is the main deduction.

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?

With no output schema and no annotations, the description still specifies the return shape (10 label rows + signed crop URLs), the de-identification guarantees, and the identity-field caveat. An agent has everything needed to call it and interpret the result.

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 100%, so quote_id, x_payment, and payment_tx are already documented with their own semantics. The description reiterates the payment_tx flow (amount, chain, wallet) but that content is duplicated in the schema, and it adds nothing about quote_id or x_payment beyond the structured fields. Baseline 3 is appropriate.

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?

States a specific verb and resource — returns a 10-crop trial slice of the geo-stripped commercial-truck detection corpus — and explicitly contrasts it with the full corpus (get_spotter_cv, $50) and the free preview (get_spotter_cv_profile). An agent knows exactly what this returns versus its siblings.

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?

Gives the condition for use (evaluate crop + de-identification quality before committing to the full corpus) and names both alternatives by name. It also sets expectations on when it is not useful for identity work (usdot/carrier null in the unlabeled majority — judge the images, not the identity fields).

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