Skip to main content
Glama

BRAINIAC Physical & IoT Security

Build building-security timeline

physical-security_building-security-timeline

Generate a chronological security timeline from caller-supplied building events. Timeline entries are observed events, not confirmed incidents. Price $0.05 USDC. POST /api/v1/physical-security/building-security-timeline. 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_building-security-timeline"
  }
}

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.7/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. It usefully discloses pricing, the POST endpoint, and that unpaid calls return 402 without running, plus the important semantic caveat that entries are observed events, not confirmed incidents. However, it omits auth requirements, mutation/storage behavior, idempotency, rate limits, and response characteristics.

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?

The description is front-loaded and efficient, with each sentence contributing purpose, semantic caveat, price, endpoint, or payment behavior. Slight redundancy exists between the price statement and the 402/no-run sentence, but it remains compact.

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 complex tool with 12 parameters, nested event objects, no annotations, and no output schema, the description is materially incomplete. It explains purpose and payment behavior but leaves parameter usage, input format choices, and output shape largely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 12 parameters with 0% description coverage, including nested event fields and tuning parameters like anomalyStdev, offlineMinutes, tailgateSeconds, and correlationWindowMinutes. The description only vaguely references 'caller-supplied building events' and does not explain how to use events, csv, json, text, files, asOf, or any tuning 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?

The description states a specific verb and resource: generating a chronological security timeline from caller-supplied building events. It also clarifies that timeline entries are observed events rather than confirmed incidents, which helps distinguish the output from sibling detection/analysis tools, though it does not explicitly name alternatives.

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?

Usage is only implied by 'from caller-supplied building events' and the observed-vs-confirmed caveat. There is no explicit guidance on when to choose this timeline tool over sibling tools such as alarm correlation or anomaly detection, nor are prerequisites or exclusions stated.

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