Skip to main content
Glama

BRAINIAC Physical & IoT Security

Detect tailgating signals

physical-security_access-tailgating-signal-detect

Identify possible tailgating using caller-supplied access grants correlated with nearby motion/occupancy or unbadged second passages. Not visually confirmed. Price $0.05 USDC. POST /api/v1/physical-security/access-tailgating-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_access-tailgating-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 genuinely useful non-schema behavior: a $0.05 USDC price, and that unpaid calls return 402 and do not execute. It also flags the output as unverified ('Not visually confirmed'). What it omits is any sense of result shape, confidence semantics, or volume limits for a 12-parameter analytic tool.

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 and method before operational facts (price, endpoint, payment failure). Nothing is padded or repetitive, though the raw endpoint path adds little for an agent that will not construct the request URL by hand.

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, nested objects, no annotations, and no output schema, the description is thin. Crucially it never explains how to supply the input data despite offering four mutually redundant transports (csv, json, text, file/files), and it gives no notion of what a detected signal contains, which is the main thing an agent needs before paying per call.

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 and file objects, so the description must compensate and largely fails to. It gestures at the event data ('access grants', 'motion/occupancy', 'unbadged second passages') but says nothing about the csv/json/text/file/files payload options, asOf, anomalyStdev, offlineMinutes, tailgateSeconds, or the two window parameters — the ones most likely to change results.

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 possible tailgating') and explains the detection method: caller-supplied access grants correlated with nearby motion/occupancy or unbadged second passages. The scope note 'Not visually confirmed' implicitly separates it from camera-based siblings, but no sibling is named, so routing still requires inference from the title.

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 rather than stated: the agent must supply access-grant and motion/occupancy data, and the result will be a heuristic signal rather than a confirmed incident. There is no explicit when-to-use, when-not-to-use, or 'use X instead' guidance relative to door-access-pattern-detect or alarm-correlation-analyze, leaving the agent to guess between them.

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