CVAT MCP

cvat_get_task_annotations

Retrieve all annotations for a specific CVAT task by providing its unique task ID.

Instructions

Get task annotations from GET /api/tasks/{id}/annotations/.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "<taskId>"
    },
    "name": "cvat_get_task_annotations"
  }
}

Input Schema

Name	Required	Description	Default
`taskId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 14, 2026

TDQS

D1.8/5.0

Behavior1/5

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

No annotations are present, and the description does not disclose behavioral details such as whether the operation is read-only, authentication requirements, or data format. The description merely restates the endpoint path, adding no behavioral insight beyond the name.

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

Conciseness2/5

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

The description is a single sentence of 9 words, which is concise but lacks structure and does not convey essential information beyond the name. It is under-specified rather than efficiently compact.

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

Completeness1/5

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

Given the absence of annotations, output schema, and parameter explanations, the description is insufficient for an agent to understand the tool's behavior, prerequisites, or return values. It fails to provide a complete context for reliable invocation.

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 input schema has 0% description coverage, and the description does not explain the 'taskId' parameter beyond its schema definition (integer, minimum 1). No context is provided about what identifiers are valid or how to obtain them.

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

Purpose3/5

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

The description states the action (get annotations) and references the specific API endpoint, which clarifies the resource. However, it does not differentiate from sibling tools like cvat_get_task (which gets task metadata) or cvat_replace_task_annotations, leaving ambiguity about scope.

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 like cvat_get_task or cvat_list_tasks. There are no prerequisites or context for appropriate invocation.

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

Deploy Server