Skip to main content
Glama

BRAINIAC Physical & IoT Security

Analyze IoT device behaviour

physical-security_iot-device-behavior-analyze

Identify unusual IoT device behaviour from caller-supplied telemetry (reporting gaps, outliers, unexpected reboot/config events). Devices are never contacted or controlled. Price $0.04 USDC. POST /api/v1/physical-security/iot-device-behavior-analyze. Unpaid calls return 402 and do 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": "physical-security_iot-device-behavior-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
eventsNo
anomalyStdevNo
offlineMinutesNo
tailgateSecondsNo
doorWindowMinutesNo
correlationWindowMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose real behavior: devices are never contacted or controlled (the key safety trait for an IoT tool), the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 without running. It omits idempotency, latency, and what the analysis returns, keeping it short of a 5.

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 followed by safety, price, and error behavior; no filler. Slightly dense as a list of facts, but every sentence carries information an agent needs.

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

Completeness2/5

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

For a 12-parameter tool with nested objects, no annotations, and no output schema, the description covers purpose and commercial/error behavior but leaves the entire input contract unexplained — how to supply events vs CSV/JSON/file uploads, and how the window/stdev parameters change results. An agent could not confidently assemble a correct call from this alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, including nested event objects and tuning knobs (anomalyStdev, offlineMinutes, tailgateSeconds, correlationWindowMinutes), yet the description explains none of them. Only the vague phrase 'caller-supplied telemetry' gestures at the events/csv/json/file inputs and gives no hint on which input form to choose or how thresholds affect detection.

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?

Names a specific verb and resource ('Identify unusual IoT device behaviour') and enumerates concrete detections: reporting gaps, outliers, unexpected reboot/config events. It is distinguishable from siblings by scoping to IoT device telemetry, though it never explicitly contrasts itself with sensor-event-anomaly-detect or the other signal detectors.

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?

'From caller-supplied telemetry' implies the caller must bring the data rather than pointing the tool at a live system, and the 402 note tells the agent the call will not execute unpaid. There is no explicit when-to-use/when-not or routing to a sibling detector, so the guidance stays implied.

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