Skip to main content
Glama

BRAINIAC Physical & IoT Security

Detect unusual door-access patterns

physical-security_door-access-pattern-detect

Identify unusual access patterns from caller-supplied door-entry logs (denials, forced doors, held-open, after-hours). Not a confirmed intrusion. Price $0.04 USDC. POST /api/v1/physical-security/door-access-pattern-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_door-access-pattern-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 bears the full disclosure burden; it does add real value by stating price ($0.04 USDC) and the payment-gate behavior ('unpaid calls return 402 and do not run'), plus the caveat that findings are not a confirmed intrusion. It omits other behavioral traits such as latency, data retention of submitted logs, determinism, and how empty inputs are handled.

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 what the tool detects and its advisory nature; pricing, endpoint, and failure behavior follow as compact metadata. Nothing is padded, though the raw endpoint path is of marginal use to an agent.

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 file and event objects, no output schema, and no annotations, the description is thin — it never explains which input channel to use, what shape the door-entry logs should take, or what the analysis returns. The payment and interpretation caveats are good, but the input-contract gap is significant.

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?

Twelve parameters with 0% schema description coverage and no enum documentation, and the description explains none of them — not the csv/json/text/file/files input channels, not events, asOf, anomalyStdev, tailgateSeconds, doorWindowMinutes, or correlationWindowMinutes. The parenthetical signal list only loosely gestures at the events.outcome values (denied/forced/held), leaving the agent to guess at every threshold and format parameter.

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 ('Identify unusual access patterns from caller-supplied door-entry logs') and enumerates the signal types it looks for (denials, forced doors, held-open, after-hours), which distinguishes it from camera-tampering or perimeter-breach siblings. It stops short of explicitly naming when a sibling detector is the better choice.

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?

The 'caller-supplied door-entry logs' phrasing implies the agent must bring its own log data, and 'Not a confirmed intrusion' sets expectations for the output. However, there is no guidance on which sibling tool to prefer, no prerequisite on log format/required fields, and no note on what happens with the zero-required-parameter signature.

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