Skip to main content
Glama

IvedaAI: Ainvr

ivedaai_ainvr
Destructive

Manage Ainvr video analytics clusters: list, create, update, delete, validate connections, and sync cameras.

Instructions

IvedaAI API — Ainvr operations. Response JSON: "status" is the HTTP status code; "truncated"/"timedOut" flag a cut-off response.

GET /api/ainvrs — List Ainvrs query: offset?:integer, page?:any, pageNumber?:integer, pageSize?:integer, paged?:boolean, size?:any, sort?:any, sort.sorted?:boolean, sort.unsorted?:boolean, unpaged?:boolean

POST /api/ainvrs — Create Ainvr body: AinvrRequest — required: host, name, password, port, scheme, username; ivedaai_get_schema for all fields

PUT /api/ainvrs — Sync Cluster(s) by id query: ainvrIds*:integer, notify?:boolean

DELETE /api/ainvrs/{ainvrId} — Delete ainvr by id path: ainvrId*:integer

GET /api/ainvrs/{ainvrId} — Find Ainvr by id path: ainvrId*:integer

PATCH /api/ainvrs/{ainvrId} — patch Ainvr path: ainvrId*:integer body: AinvrRequest — required: host, name, password, port, scheme, username; ivedaai_get_schema for all fields

PUT /api/ainvrs/{ainvrId} — Update Ainvr path: ainvrId*:integer body: AinvrRequest — required: host, name, password, port, scheme, username; ivedaai_get_schema for all fields

PUT /api/ainvrs/{ainvrId}/cameras — Sync Ainvr Cameras path: ainvrId*:integer

POST /api/ainvrs/validate — Check Ainvr connection body: AinvrRequest — required: host, name, password, port, scheme, username; ivedaai_get_schema for all fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoJSON request body, or form field values when uploading a file.
fileNoLocal file to upload, for operations that accept a file.
pathNoPath parameters, e.g. { "cameraId": 12 }
queryNoQuery string parameters for this operation.
operationYesWhich API operation to call, from the list in this tool's description.
Behavior4/5

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

The description adds behavioral context beyond annotations by explaining the response envelope ('status', 'truncated'/'timedOut'), required fields for bodies, and operation side effects like sync/delete. It aligns with the destructiveHint annotation without contradiction.

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 endpoint list is compact and front-loaded with the response note. Repetition of the same body requirement for POST, PATCH, and PUT adds slight redundancy, but overall it is an efficient structured reference for a multi-operation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All 9 operations are described with their parameters and the response envelope is explained. However, missing examples, error handling, and semantic details for body parameters leave some gaps for such a complex tool with no output schema.

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

Parameters5/5

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

Each endpoint's query, path, and body parameters are explicitly listed with types and required markers (e.g., ainvrIds*:integer, host required). The description also directs to ivedaai_get_schema for full field details, far exceeding the generic schema's empty parameter definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates 9 distinct operations with specific verbs (List, Create, Sync, Delete, Find, Patch, Update, Sync Cameras, Validate) targeting the Ainvr resource. This provides concrete purpose and distinguishes the tool from siblings by resource and action.

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?

The description references ivedaai_get_schema for field definitions and specifies required body fields, but it does not explain when to use this tool over closely related siblings like ivedaai_nvr, nor does it provide any exclusions or alternative-tool guidance. The usage context is implied but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WillORepO/ivedaAI-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server