Anava MCP Server

anava_monitor_events

Track real-time camera events such as motion or object detection, set monitoring duration, and specify event types for efficient surveillance using Anava MCP Server.

Instructions

Monitor camera for real-time events

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": "anava_monitor_events"
  }
}

Input Schema

Name	Required	Description
`camera`	No	Camera name or use default if not specified
`duration`	No	Monitoring duration in seconds
`event_types`	No	Event types to monitor (e.g., ["motion", "object"])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2025

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'monitor for real-time events' but lacks details on permissions, rate limits, what happens during monitoring (e.g., streaming, alerts), or output format. This is inadequate for a tool with potential real-time implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste, front-loading the core purpose. It's appropriately sized for the tool's complexity, making it easy to parse quickly.

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?

Given the tool's real-time monitoring nature, no annotations, and no output schema, the description is incomplete. It fails to explain behavioral aspects like how events are reported, error handling, or dependencies, leaving significant gaps for an AI agent to use it effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters (camera, duration, event_types). The description adds no additional meaning beyond what the schema provides, such as examples for event_types or default behaviors, meeting the baseline for high coverage.

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 clearly states the action ('monitor') and resource ('camera for real-time events'), making the purpose understandable. It distinguishes from sibling tools like 'anava_capture_image' (static capture) and 'anava_get_events' (retrieval of past events) by focusing on real-time monitoring, though it doesn't explicitly name these 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?

No guidance is provided on when to use this tool versus alternatives. The description mentions 'real-time events' but doesn't specify scenarios, prerequisites, or exclusions compared to siblings like 'anava_capture_analyze' or 'anava_get_events', leaving usage context unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server