Skip to main content
Glama
Sign In
anki-connect-mcp

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

operations.get

operations_get
Read-only

Poll a long-running operation by ID to check status and retrieve its typed result or error, so you can track completion and handle failures.

Instructions

Poll operation status and its eventual typed result/error.

Anki-Connect method operations.get. Scope: application. Effect: read. Completion: completed. Undo: none.

Possible errors: internalError, invalidParams, notFound.

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": {
      "operationId": "<operationId>"
    },
    "name": "operations_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes`operationId` from the operation handle returned by a long-running tool (or by `operations_get`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds useful metadata beyond that: scope 'application', 'Completion: completed', 'Undo: none', and an explicit error set (internalError, invalidParams, notFound). It stops short of explaining what a terminal state looks like or whether the operation record expires.

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 core purpose is front-loaded in the first sentence, and the remaining metadata is compact and scannable. The 'Effect: read' line partly restates the readOnlyHint annotation, which is minor redundancy.

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?

For a single-parameter polling tool with no output schema, the description covers scope, effect, completion semantics, undo behavior, and the error surface. The one gap is that the 'typed result/error' payload shape is never characterized, leaving the agent to discover it at call time.

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 coverage is 100% and the single operationId property already explains that it comes from an operation handle returned by a long-running tool. The description adds nothing further about the parameter, so the baseline 3 applies.

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 ('Poll operation status and its eventual typed result/error'), which clearly distinguishes it from the sibling operations_cancel. It does not name that sibling explicitly, so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The verb 'Poll' implies repeated invocation after a long-running tool returns a handle, but the description never says when to call this versus operations_cancel, or whether polling should continue until a terminal state. The only context about handle origin lives in the schema property description, not the tool description.

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

Deploy Server

Other Tools