Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Check industrial protocol compatibility

robotics-intelligence_protocol-compatibility-check
Read-onlyIdempotent

Compare caller-supplied required versus available industrial protocol names, versions, and features. Protocol specifications are not invented. Price $0.03 USDC. POST /api/v1/robotics-intelligence/protocol-compatibility-check. 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_protocol-compatibility-check"
  }
}

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.
protocolCountNoprotocolCount. Number.
apiKeyRequiredNoapiKeyRequired. Boolean.
compatibleCountNocompatibleCount. Number.
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 read-only, idempotent, non-destructive and open-world traits, so the bar is lower; the description still adds real behavioral context: results are grounded in supplied data ("specifications are not invented"), there is a $0.03 USDC charge, and an unpaid call returns x402 payment terms without executing. That last point materially changes how an agent should call it.

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 comparison semantics, then the non-fabrication guarantee, then price and endpoint, then the unpaid-call behavior. Every sentence carries information an agent needs; nothing is padding.

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 an output schema exists, return values need not be described, and the description covers the essential calling contract. The remaining gap is what happens when the protocols array is empty or only one side is supplied — a meaningful edge case for a comparison tool with zero required parameters.

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 100%, so baseline is 3, but the description elevates it by pointing at the semantically important input — the protocols array with required/available roles, names, versions and features — while the schema describes that array only generically. It implicitly signals that the other 13 parameters are optional supplementary context.

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?

States a specific verb and resource: "Compare caller-supplied required versus available industrial protocol names, versions, and features." That is precise enough to distinguish it from sibling analysis tools like cycle-time-analyze or ros-topic-schema-diff, though it does not name them explicitly.

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 implied by "caller-supplied required versus available" — the agent must supply protocol data — and the payment note clarifies that an unpaid call does not run. However, there is no explicit when-to-use versus alternatives guidance or any exclusion conditions.

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