Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Analyze robot cycle time

robotics-intelligence_cycle-time-analyze
Read-onlyIdempotent

Summarize caller-supplied robot cycle durations by robot, workcell, and program. Missing durations are not invented when start/end times are absent. Price $0.04 USDC. POST /api/v1/robotics-intelligence/cycle-time-analyze. 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_cycle-time-analyze"
  }
}

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.
cyclesNocycles. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
groupCountNogroupCount. Number.
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?

Annotations already declare readOnly, idempotent, and non-destructive, so the description earns credit for the operational facts they cannot carry: the $0.04 USDC price, that an unpaid call returns x402 payment terms and does not execute, and that durations are not fabricated when start/end times are missing. That payment-gating behavior is essential and would otherwise be a surprise failure. It does not describe response content, though an output schema exists to cover that.

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 purpose, then data-integrity behavior, then price, then endpoint and failure mode. Nothing is padded or redundant.

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?

For a 14-parameter paid endpoint, the description omits which input channel to use among csv/json/text/cycles/file/files and how they combine, which is the main decision an agent faces. Payment behavior and missing-data handling are covered, and the output schema relieves it of return-value duty, but the input-selection gap is material.

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 nominally 100%, but the schema text is boilerplate ("csv, string, length 0 to 200000"), so the description adds real meaning: durations come from cycles, grouping keys are robotId/workcellId/program, and durationSec can be given directly or derived from startedAt/endedAt. It says nothing about the many other input channels (csv, json, text, files, samples, opcuaTags), leaving how to deliver data ambiguous.

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?

"Summarize caller-supplied robot cycle durations by robot, workcell, and program" gives a concrete verb, resource, and aggregation dimensions. The word "caller-supplied" signals it analyzes data you pass in rather than fetching live telemetry, which implicitly separates it from siblings like telemetry-anomaly-detect. It stops short of naming any sibling explicitly, so it does not fully lock in differentiation.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The implicit guidance (bring your own cycle data, supply start/end or duration) is inferable from "caller-supplied" and the missing-duration sentence, but an agent must reason about it rather than being told.

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