Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Build robot workcell performance report

robotics-intelligence_workcell-performance-report
Read-onlyIdempotent

Aggregate rosbag parse, schema diff, anomalies, cycle time, downtime, OPC UA tags, PLC alarms, maintenance, and protocol compatibility from caller-supplied records only. Price $0.08 USDC. POST /api/v1/robotics-intelligence/workcell-performance-report. 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_workcell-performance-report"
  }
}

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
asOfNoasOf. String.
statusNostatus. String.
findingsNofindings. Array.
sectionsNosections. Object.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
machineCommandsIssuedNomachineCommandsIssued. Boolean.
liveEquipmentConnectedNoliveEquipmentConnected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive), the description discloses economics and failure behavior: $0.08 USDC, the POST path, and that an unpaid call returns x402 payment terms without executing. That is exactly the kind of context annotations cannot carry. The 'caller-supplied records only' scoping is useful, though it sits in slight tension with openWorldHint=true and no explanation is given.

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?

Three sentences, front-loaded with the capability, then cost, then endpoint and payment-failure behavior. The long enumeration in sentence one is dense but each item is load-bearing. No filler.

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

Completeness5/5

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

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description fills the remaining gaps an agent needs: what it aggregates, that input must be supplied by the caller, the price, the transport, and what happens when payment is absent.

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 coverage is 100% and the nested objects are documented field by field, so the schema does the heavy lifting. The description's enumeration of domains does map onto the top-level array parameters (cycles, downtime, samples, schemas, opcuaTags, plcAlarms, maintenance, protocols), but it adds no guidance on which to supply or how they interact in the aggregation.

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 opens with a concrete verb, 'Aggregate', and enumerates the exact record domains it combines (rosbag parse, schema diff, anomalies, cycle time, downtime, OPC UA tags, PLC alarms, maintenance, protocol compatibility). That makes the composite nature clear and implicitly contrasts with the single-domain siblings, though it never names one, so the differentiation is inferential rather than explicit.

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?

Usage is only implied: this is the roll-up tool that consumes caller-supplied records across all the sibling domains. There is no explicit 'use this when you want one combined report, use the individual analyzers otherwise' statement, and no prerequisites about needing records in the first place beyond 'caller-supplied records only'.

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