Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Detect robot telemetry anomalies

robotics-intelligence_telemetry-anomaly-detect
Read-onlyIdempotent

Flag caller-supplied telemetry samples whose z-score is outside ±3 of the supplied series mean. Live equipment is not contacted. Price $0.04 USDC. POST /api/v1/robotics-intelligence/telemetry-anomaly-detect. 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_telemetry-anomaly-detect"
  }
}

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
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
seriesCountNoseriesCount. Number.
anomalyCountNoanomalyCount. Number.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
machineCommandsIssuedNomachineCommandsIssued. Boolean.
liveEquipmentConnectedNoliveEquipmentConnected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety bar is low; the description adds genuinely non-obvious behavior: no live equipment is contacted, cost is $0.04 USDC, and an unpaid call returns x402 payment terms without executing. It does not describe failure modes (e.g., insufficient samples for a mean) or result shape, which keeps it below a 5 given an output schema exists.

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?

Four short sentences, front-loaded with the detection rule, then the offline guarantee, then cost, then endpoint and unpaid-call behavior. Nothing is redundant and each sentence adds a distinct operational fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Payment gating and the offline guarantee are well covered, and the output schema relieves the description of explaining returns. But with zero required parameters and seven alternative input channels (samples, cycles, downtime, opcuaTags, plcAlarms, csv/json/text, file/files), the description never says which payload actually drives the z-score computation, leaving a significant ambiguity for a complex nested tool.

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 schema already documents all 14 parameters and this is the baseline case. The description adds only the concept of a 'supplied series' whose mean drives the threshold, without clarifying which input channel (samples, csv, json, text, file/files) or grouping field (topic/field/robotId) defines that series.

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 ('Flag telemetry samples') plus the exact detection rule ('z-score outside ±3 of the supplied series mean'), which pins down semantics no sibling tool covers. An agent can distinguish it from rosbag-telemetry-parse or cycle-time-analyze without opening the schema.

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?

'Caller-supplied telemetry samples' and 'Live equipment is not contacted' imply when this tool applies (offline scoring of data you already have, not live monitoring), which is useful context. However, it never names an alternative or states when not to use it, so routing guidance beyond the offline-vs-live hint is left to inference.

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