Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Parse ROS bag telemetry exports

robotics-intelligence_rosbag-telemetry-parse
Read-onlyIdempotent

Parse caller-supplied ROS bag topic CSV/JSON exports into labeled telemetry samples. Binary .bag/.mcap files are not fully decoded and live robots are not contacted. Price $0.04 USDC. POST /api/v1/robotics-intelligence/rosbag-telemetry-parse. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "robotics-intelligence_rosbag-telemetry-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
filesNofiles, array. Optional.
cyclesNocycles, array. Optional.
samplesNosamples, array. Optional.
schemasNoschemas, array. Optional.
downtimeNodowntime, array. Optional.
opcuaTagsNoopcuaTags, array. Optional.
plcAlarmsNoplcAlarms, array. Optional.
protocolsNoprotocols, array. Optional.
maintenanceNomaintenance, array. Optional.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
topicsNotopics. Array.
samplesNosamples. Array.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
topicCountNotopicCount. Number.
limitationsNolimitations. Array.
sampleCountNosampleCount. Number.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
machineCommandsIssuedNomachineCommandsIssued. Boolean.
liveEquipmentConnectedNoliveEquipmentConnected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses the price ($0.04 USDC), the HTTP method and endpoint, and the payment gating behavior: an unpaid call returns x402 terms and does not execute. It also clarifies that binary ROS bag files are not fully decoded and live robots are not contacted, giving the agent crucial operational context for a paid, read-only parse.

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 four front-loaded sentences with no wasted words. It moves logically from purpose to scope limitations to pricing and payment behavior, and each sentence carries information not available in the structured fields.

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?

Given the tool's complexity (14 optional parameters, nested objects, an output schema), the description covers purpose, scope limits, pricing, and payment failure behavior. The output schema handles return values, and annotations handle safety, so the remaining gap is minor: it does not explain what 'labeled' means in the output, though that is likely defined in the output schema.

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 description coverage is 100%, so the input schema already documents all 14 parameters thoroughly. The description adds no parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb ('Parse') and resource ('caller-supplied ROS bag topic CSV/JSON exports') and the output ('labeled telemetry samples'). It also scopes the tool by ruling out binary .bag/.mcap decoding and live robot contact, but it does not explicitly differentiate itself from sibling tools such as ros-topic-schema-diff or telemetry-anomaly-detect.

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?

The description implies usage by specifying that the tool works on CSV/JSON exports and not binary files or live robots, which serves as partial when-not guidance. However, it never names an alternative tool for binary decoding or analysis, leaving the agent to infer alternatives from sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources