Skip to main content
Glama

BRAINIAC Physical & IoT Security

Detect perimeter-breach signals

physical-security_perimeter-breach-signal-detect

Analyze caller-supplied perimeter sensor events for possible breaches. Multi-sensor alarms raise confidence; still not a confirmed physical breach. Price $0.04 USDC. POST /api/v1/physical-security/perimeter-breach-signal-detect. 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_perimeter-breach-signal-detect"
  }
}

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.1/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 behavioral burden, and it does disclose useful operational traits: $0.04 USDC pricing, POST endpoint, and that unpaid calls return 402 without executing. It also flags the confidence semantics of multi-sensor alarms. It says nothing about rate limits, determinism, return shape, or how uploaded files versus inline events are treated.

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 with the purpose front-loaded and no filler; price, endpoint and payment behavior are each compressed to a clause. The endpoint path is arguably redundant given the tool name, but nothing is wasted.

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 tool with 12 parameters, a nested 20-field event object, five input channels, and no output schema and no annotations, the description is far too thin on input shape and says nothing about what comes back. An agent knows what the tool is for and what it costs, but not what to send or how to interpret the response.

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 0% across 12 parameters, so the description would need to compensate and largely does not. 'Caller-supplied sensor events' hints at the events array, but the five alternate payload channels (csv, json, text, file, files) and the tuning knobs (correlationWindowMinutes, tailgateSeconds, offlineMinutes, anomalyStdev, asOf) go entirely unexplained. Baseline 3 applies since the schema still constrains types and bounds even without inline descriptions.

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: analyze caller-supplied perimeter sensor events for possible breaches. The 'perimeter-breach' framing does differentiate it from sibling concerns like tailgating or camera tampering, though it never names an alternative explicitly.

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?

No when-to-use or when-not guidance and no routing to siblings such as sensor-event-anomaly-detect or alarm-correlation-analyze, which an agent would need to choose correctly. The only guidance-adjacent content is the caveat that multi-sensor alarms are 'still not a confirmed physical breach,' which tells the agent how to read output rather than when to call the tool.

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