Skip to main content
Glama

BRAINIAC Physical & IoT Security

Correlate multi-sensor alarms

physical-security_alarm-correlation-analyze

Correlate alarms from multiple caller-supplied sensors into possible incident groups using time windows. Correlation is not confirmation of a physical incident. Price $0.05 USDC. POST /api/v1/physical-security/alarm-correlation-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_alarm-correlation-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

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful operational facts: a $0.05 USDC price, a 402 response for unpaid calls that do not run, and the POST endpoint. It still omits whether the operation mutates or stores anything, rate limits, and what the returned incident groups contain, so it is partial rather than complete.

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 tight sentences with the core function front-loaded and the cost/access constraints following. The endpoint string is arguably boilerplate but is standard and cheap; nothing is padded.

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 deeply nested event objects and no output schema, the description leaves the caller without an explanation of input shapes or return values. The pricing and 402 behavior are covered well, but the substantive calling complexity is not.

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 with roughly 25 fields each. The description only obliquely hints at 'time windows' (correlationWindowMinutes) and 'caller-supplied sensors' (events), leaving asOf, csv/json/text/file/files alternatives, anomalyStdev, offlineMinutes, tailgateSeconds, and doorWindowMinutes entirely unexplained.

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 states a specific verb ('Correlate'), a specific input ('alarms from multiple caller-supplied sensors'), and a specific output ('possible incident groups using time windows'), which is clear enough for an agent to distinguish it from sibling signal-detection tools. It stops short of naming a sibling alternative, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance given is interpretive ('Correlation is not confirmation of a physical incident'), which is a useful caveat but not a when-to-use rule. There is no statement of when to prefer this over anomaly-detect or tailgating-detect siblings, no prerequisites, and no exclusions.

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