Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Estimate robot maintenance intervals

robotics-intelligence_maintenance-interval-estimate
Read-onlyIdempotent

Estimate remaining hours/cycles to caller-supplied maintenance intervals. OEM schedules are not invented. Price $0.04 USDC. POST /api/v1/robotics-intelligence/maintenance-interval-estimate. 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_maintenance-interval-estimate"
  }
}

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.
dueCountNodueCount. Number.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
itemCountNoitemCount. Number.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
machineCommandsIssuedNomachineCommandsIssued. Boolean.
liveEquipmentConnectedNoliveEquipmentConnected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the price ($0.04 USDC), the transport (POST /api/v1/robotics-intelligence/maintenance-interval-estimate), and the x402 payment flow: an unpaid call returns payment terms and does not execute. That is exactly the operational context an agent needs before invoking a paid endpoint, and it does not conflict with readOnlyHint/idempotentHint.

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?

Four short sentences, front-loaded with the purpose, then the non-invention caveat, then price/route, then the payment failure mode. The route string is mildly redundant with the tool name but is legitimate machine-readable context; nothing else is wasted.

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?

The tool is complex (14 optional top-level parameters, nested arrays, a file upload path), but an output schema exists so return values need not be described. The description covers purpose, cost, protocol, and failure behavior; the main remaining gap is that it never says which input shapes are actually needed to produce an estimate, leaving an agent with all-optional parameters unsure what to 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%, so the 14 parameters and their nested fields are already documented structurally. The description contributes only the high-level hint that intervals are caller-supplied (pointing at the maintenance array's intervalHours/intervalCycles), without explaining asOf or how csv/json/text/file inputs relate to the structured arrays. Baseline 3 is appropriate.

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 ('Estimate remaining hours/cycles to caller-supplied maintenance intervals') and adds a scoping constraint ('OEM schedules are not invented') that tells the agent this tool computes from data rather than looking up manufacturer schedules. No sibling in the list touches maintenance, so there is no ambiguity to resolve.

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 the name and the 'caller-supplied intervals' phrasing, which signals the caller must bring the interval data. There is no explicit when-to-use versus an alternative, and no statement of prerequisites such as which inputs must be present for an estimate to be produced.

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