Skip to main content
Glama

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

by io.rtkmotion
OverviewDiscussionsAdmin

get_threat_summary

Location threat assessment for risk_underwriting, facility_security_audit, or insurance_risk_modeling. Lite ($0.50): confidence-scored alerts, event distribution. Full ($1.00): + enriched entities, temporal context, corroboration scoring. Latency <200ms. Pay USDC on Base (chain 8453, USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) to RTK wallet 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C; pass tx hash as payment_tx. Eth/Solana: /.well-known/x402. Browse ThreatIntel via browse_catalog first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNo'lite' ($0.50 USDC) = summary only; 'full' ($1.00 USDC) = summary + enriched flagged itemslite
regionNoRegion, e.g. 'Virginia' or 'Florida'. Required to resolve the R2 path.
locationYesLocation slug, e.g. 'culpeper-town' or 'fbcl-longwood'
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.50 (lite) or $1.00 (full) 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 / 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. Changed2 schema fields changed
    • changedInput schema / properties / payment_tx / description
      Previous value: -"Transaction hash proving USDC payment"New value: +"USDC transaction hash. Send $0.50 (lite) or $1.00 (full) USDC on Base to 0x6C11F8a21f7ca922F483Ed21C3b6c2d9B305B10C, then pass tx hash here."
    • changedInput schema / properties / tier / description
      Previous value: -"'lite' ($0.10) = summary only, 'full' ($0.25) = summary + flagged items"New value: +"'lite' ($0.50 USDC) = summary only; 'full' ($1.00 USDC) = summary + enriched flagged items"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses pricing per tier, latency (<200ms), payment requirements (USDC on Base with specific chain/wallet, or x402 on Eth/Solana), and the nature of the response (confidence-scored alerts, event distribution, enriched entities, etc.). This is substantial behavioral context beyond annotations.

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 front-loaded with purpose, then logically organizes pricing, latency, payment instructions, and discovery tip. It is somewhat dense but each sentence adds necessary operational detail.

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?

With no output schema, the description provides high-level response components but doesn't detail the full response structure. It covers payment, tiers, latency, and use cases, and points to browse_catalog for further discovery, making it fairly complete for a payment-gated tool.

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 payment flow context (wallet address, chain, tx hash as payment_tx) that supplements the schema, clarifying how to pay and at what price. It reinforces the tier enum values with costs.

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 'Location threat assessment' for specific use cases (risk_underwriting, facility_security_audit, insurance_risk_modeling) and differentiates lite vs full tiers. This is a specific verb+resource+scope, and while it doesn't compare to siblings directly, the purpose is unmistakable.

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 states when to use (for risk_underwriting, facility_security_audit, insurance_risk_modeling) and recommends browsing via browse_catalog first, implying a sequencing. It lacks explicit exclusions or direct alternative comparisons, but the context is 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