analytics-tool
Analyze space utilization, traffic flow, peak hours, and scene activity across cameras to answer business questions.
Instructions
This tool generates composite operational analytics reports by combining multiple data sources. Use it for high-level business questions about space utilization, traffic patterns, and real-time scene analysis.
It has the following modes of operation, determined by the "requestType" parameter:
space-utilization: Compare per-camera people counts against running averages at a location. Answers: "How busy is each area vs normal?"
traffic-flow: Compare ingress/egress across ALL line-crossing cameras at a location. Answers: "Which entrance gets the most traffic?"
peak-vs-average: Show hourly actual counts vs historical averages. Answers: "When is it busiest? Is today above or below normal?"
scene-intelligence: Ask a camera an arbitrary question using AI vision (e.g. "How many treadmills are in use?"). Works in real-time or at a historical timestamp.
location-summary: Generate a comprehensive multi-metric analytics summary for a location including people counts, traffic flow, and trend comparisons.
Output filtering (all tools):
includeFields(string[]): Dot-notation paths to keep in the response (e.g."vehicleEvents.vehicleLicensePlate"). Omit to return all fields.filterBy(array): Predicates to filter array items. Each entry:{field, op, value}where op is one of= != > >= < <= contains. All conditions are ANDed. Example:[{field:"vehicleLicensePlate", op:"=", value:"ABC123"}]WARNING: some tool responses exceed 400k characters — use these params to request only the data you need.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| requestType | Yes | The type of analytics report to generate. | |
| spaceUtilizationRequest | Yes | Request for space utilization report. Compares per-camera people counts against running averages. Required for 'space-utilization'. | |
| trafficFlowRequest | Yes | Request for multi-camera traffic flow report. Compares ingress/egress across all line-crossing cameras at a location. Required for 'traffic-flow'. | |
| peakVsAverageRequest | Yes | Request for peak-vs-average analysis. Shows hourly actual counts vs historical running averages. Required for 'peak-vs-average'. | |
| sceneIntelligenceRequest | Yes | Request for real-time scene intelligence. Asks a camera an arbitrary question using AI. Required for 'scene-intelligence'. | |
| locationSummaryRequest | Yes | Request for a comprehensive location analytics summary covering people counts, traffic flow, occupancy, and comparison to averages. Required for 'location-summary'. | |
| includeFields | Yes | Dot-notation field paths to include in the response (e.g. "vehicleEvents.vehicleLicensePlate"). Pass null to return all fields. WARNING: some responses can exceed 400k characters — use includeFields to request only the data you need. For high-volume tools this may be required to get a complete answer. | |
| filterBy | Yes | Filter array items in the response by field values. All conditions are ANDed. Example: [{field: "vehicleLicensePlate", op: "=", value: "ABC123"}, {field: "confidence", op: ">", value: 0.8}] Use alongside includeFields to get only the specific records and fields you need. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| spaceUtilization | No | Space utilization report with per-camera counts vs running averages. | |
| trafficFlow | No | Multi-camera traffic flow comparison with ingress/egress ranking. | |
| peakVsAverage | No | Hour-by-hour actual vs. average analysis with peak/quiet hour identification. | |
| sceneIntelligence | No | Real-time AI answer from a camera about what it currently sees. | |
| locationSummary | No | Comprehensive multi-metric location analytics summary. | |
| error | No | An error message if the request failed. |