Skip to main content
Glama

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

by io.rtkmotion
OverviewDiscussionsAdmin

search_catalog

Full-text search across motion-capture, threat-intel, and rehab-biomechanics datasets. Matches labels, paths, subject names, techniques. Returns full lesson detail with pricing so you can immediately call purchase tools. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch terms, e.g. 'kimura', 'culpeper', 'labrum'. Matched against lesson labels, path segments, and subject names.
subjectNoFilter by subject name, e.g. 'subject_1' or 'subject_2'.
verticalNoFilter by top-level vertical: 'BJJ', 'ThreatIntel', or 'PhysicalRehab'. Matches the first path segment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Search terms, e.g. 'kimura', 'BJJ', 'grappling'. Matched against lesson labels, path segments, and subject names."New value: +"Search terms, e.g. 'kimura', 'culpeper', 'labrum'. Matched against lesson labels, path segments, and subject names."
    • removedInput schema / properties / sport
      Removed value: -{
-  "description": "Filter by sport, e.g. 'BJJ'. Matches top-level path segment.",
-  "type": "string"
-}
    • addedInput schema / properties / vertical
      Added value: +{
+  "description": "Filter by top-level vertical: 'BJJ', 'ThreatIntel', or 'PhysicalRehab'. Matches the first path segment.",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • removedInput schema / properties / competitor
      Removed value: -{
-  "description": "Filter by competitor name, e.g. 'Professor' or 'Student'.",
-  "type": "string"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Search terms, e.g. 'kimura', 'BJJ', 'grappling'. Matched against lesson labels, path segments, and competitor names."New value: +"Search terms, e.g. 'kimura', 'BJJ', 'grappling'. Matched against lesson labels, path segments, and subject names."
    • addedInput schema / properties / subject
      Added value: +{
+  "description": "Filter by subject name, e.g. 'subject_1' or 'subject_2'.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / competitor / description
      Previous value: -"Filter by competitor name, e.g. 'Boca' or 'Thane'."New value: +"Filter by competitor name, e.g. 'Professor' or 'Student'."
    • changedInput schema / properties / query / description
      Previous value: -"Search terms, e.g. 'kimura', 'BJJ', 'Boca', 'grappling'. Matched against lesson labels, path segments, and competitor names."New value: +"Search terms, e.g. 'kimura', 'BJJ', 'grappling'. Matched against lesson labels, path segments, and competitor names."
  4. Added

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the operation returns full lesson detail with pricing and is free, which is useful. However, it does not mention pagination, result limits, sorting, or any potential rate limits, leaving some uncertainty about the full behavior of a search across multiple datasets.

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?

The description is two concise sentences with the primary purpose front-loaded. The second sentence adds purpose-linked output and pricing information; 'Free' is a useful qualifier. No sentence is wasted, and the structure is easy to scan.

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?

Since there is no output schema, the description compensates by explicitly stating the return value is 'full lesson detail with pricing.' It omits any mention of result ordering or pagination, which could matter for a broad catalog search, but for a simple 3-parameter search tool with strong schema coverage, the description is largely complete.

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 description coverage is 100%, establishing a baseline of 3. The description adds value by mentioning 'techniques' as a match surface beyond the schema's 'labels, path segments, and subject names,' and by tying verticals to dataset types. It enriches the query semantics without needing to restate every parameter.

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 a specific verb and resource: 'Full-text search across motion-capture, threat-intel, and rehab-biomechanics datasets.' It also lists match criteria (labels, paths, subject names, techniques) and the return type (full lesson detail with pricing), clearly distinguishing it from sibling retrieval tools like browse_catalog or get_*.

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?

The description implies usage: use this when you need to search across the catalog and get full lesson detail with pricing to proceed to purchase. It does not explicitly mention when not to use it or name alternatives like browse_catalog for browsing, but the context is clear enough for an agent to select it appropriately.

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