Skip to main content
Glama

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

by io.rtkmotion
OverviewDiscussionsAdmin

get_spotter_carrier

Full commercial-carrier sighting bundle for carrier_identity_verification, fleet_movement_corroboration, or cargo_fraud_investigation. Returns the structured sighting trail (USDOT, carrier, equipment, geo, timestamp) plus time-limited signed URLs to every de-identified truck crop (faces + bystander plates blurred). Where the subject truck is confirmed by its own USDOT/carrier markings, its plate is left unaltered; on any frame we cannot tie a plate to that confirmed truck, every plate is blurred. In practice MOST frames carry no legible plate at all — buy this for the sighting trail, not for plates. equipment is capture-derived and approximate. RTK distributes NO plate interpretation at all — no plate text or state in any record, and no plate-keyed lookup exists. Commercial carriers only — owner-operators excluded by disclosure policy. Pay $5 USDC on Base (chain 8453, USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to RTK wallet 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C; pass tx hash as payment_tx. Eth/Solana: /.well-known/x402. Free evaluation: get_spotter_carrier_profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usdotYesUSDOT number, e.g. '054283'
x_paymentNoPreferred (x402 exact / gasless): base64 X-PAYMENT payload — a signed EIP-3009 transferWithAuthorization for $5 USDC to our wallet. Redeemable only by its signer; no gas needed.
payment_txNoLegacy flow: USDC transaction hash. Send $5 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / payment_tx / description
      Previous value: -"USDC transaction hash. Send $5 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here."New value: +"Legacy flow: USDC transaction hash. Send $5 USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here."
    • addedInput schema / properties / x_payment
      Added value: +{
+  "description": "Preferred (x402 exact / gasless): base64 X-PAYMENT payload — a signed EIP-3009 transferWithAuthorization for $5 USDC to our wallet. Redeemable only by its signer; no gas needed.",
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and is highly transparent. It discloses payment requirements, privacy handling (blurring faces/bystander plates), the fact that no plate interpretation is provided, and that URLs are time-limited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains essential details but is overly long and dense, using long run-on sentences and repeated plate-related caveats. It could be structured into clearer sentences or bullet points without losing key information.

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?

Despite having no output schema, the description names the expected return fields and the nature of the image URLs. It also covers payment, privacy, and exclusions. It lacks specifics on response formatting and error cases, but is sufficient for basic invocation.

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?

The schema already covers 100% of parameters with descriptions. The description adds some context around payment flows and reiterates the wallet address, but it does not materially expand beyond the schema's parameter documentation.

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 states the tool returns a commercial-carrier sighting bundle with a structured trail and de-identified images, and explicitly identifies use cases. It is distinguishable from the sibling get_spotter_carrier_profile by noting that profile is a free evaluation, while this is the paid bundle.

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?

It gives explicit when-to-use guidance via use cases and states commercial carriers only, excluding owner-operators. It also says 'buy this for the sighting trail, not for plates' and points to get_spotter_carrier_profile for free evaluation, making alternative usage 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
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