Skip to main content
Glama

BRAINIAC Physical & IoT Security

Detect camera-tampering signals

physical-security_camera-tampering-signal-detect

Identify camera tampering indicators from caller-supplied telemetry (covered/moved/signal-loss). Scene content is not visually verified. Price $0.04 USDC. POST /api/v1/physical-security/camera-tampering-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_camera-tampering-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.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 burden and does disclose real operational facts: the analysis is based on caller-supplied telemetry only, the scene is not visually verified, the call costs $0.04 USDC, and unpaid calls return HTTP 402 without executing. What it omits is what a successful run returns and any rate/telemetry-volume expectations.

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 purpose then disclaimers then cost and transport details. No filler, though the pricing and endpoint sentences are stated somewhat telegraphically rather than integrated.

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?

This is a complex tool: 12 optional parameters, nested file objects, a large event array, no output schema, and no annotations. The description covers pricing and the non-visual limitation but says nothing about the required shape of the telemetry or expected results, leaving a substantial gap for a tool of this complexity.

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, and the description never maps its parenthetical 'covered/moved/signal-loss' to any field. Nothing explains events, anomalyStdev, offlineMinutes, tailgateSeconds, doorWindowMinutes, correlationWindowMinutes, or the csv/json/text/file/files input variants, so the caller must reverse-engineer the schema.

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?

Uses a specific verb and resource ('Identify camera tampering indicators') and names the three signal classes it looks for (covered/moved/signal-loss). It also scopes the input to 'caller-supplied telemetry', which sets it apart from visual-analysis tools, though it never names a sibling to contrast with.

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?

'Scene content is not visually verified' implicitly tells the caller this is a signal-correlation path rather than a video/VLM check, which is useful selection context. However, there is no explicit when-to-use, when-not-to-use, or named alternative among the sibling detection tools, so routing is still largely inferred.

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