Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Cluster PLC alarms

robotics-intelligence_plc-alarm-cluster
Read-onlyIdempotent

Cluster caller-supplied PLC alarm log events by controller, code, and area. Live PLCs are not contacted. Price $0.04 USDC. POST /api/v1/robotics-intelligence/plc-alarm-cluster. 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_plc-alarm-cluster"
  }
}

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.
clusterCountNoclusterCount. 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 cover readOnly, idempotent, non-destructive, and open-world, so the bar is lower. The description adds genuinely non-structured behavior: a fixed $0.04 USDC price, the POST endpoint, and the x402 gating rule that an unpaid call returns payment terms and performs no work — exactly the payment semantics an agent cannot get from annotations.

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 operation and scope, followed by the constraint, price, and endpoint. No sentence is redundant and nothing is buried.

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 and the schema documents all 14 optional parameters, so the description is not required to explain return values. The remaining gaps — which payload field is authoritative and when to prefer this over a sibling analysis — are minor against what the structured fields already supply.

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% across all 14 parameters, so the schema already carries the documentation burden and baseline 3 applies. The description contributes only the grouping dimensions (controller, code, area), which map to plcAlarms item fields but are not tied to a specific parameter name.

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 gives a specific verb (cluster) and resource (caller-supplied PLC alarm log events) plus the three grouping keys — controller, code, and area — which no sibling tool claims. It stops short of naming a sibling or explicitly contrasting with, say, downtime-root-cause, so the boundary is inferred rather than stated.

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?

'Live PLCs are not contacted' implies the caller must supply the alarm data inline, which is useful selection context. However, there is no explicit when-to-use framing versus the other robotics-intelligence analysis tools, and nothing tells the agent which payload field (e.g. plcAlarms) is the operative input.

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