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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

application.exit

application_exit
Destructive

Acknowledge a close request and schedule a normal Anki application exit after the response is sent. Native save or sync dialogs can still cancel the shutdown.

Instructions

Acknowledge a close request, then initiate normal application close after sending the response.

Accepted means the request was scheduled, not that Anki has exited. Native close/save/sync dialogs may cancel it. Retain timer/callback ownership; process exit prevents polling a final operation result.

Anki-Connect method application.exit. Scope: application. Effect: lifecycle. Completion: completed. Undo: none.

Possible errors: internalError, invalidParams.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, readOnlyHint=false) by disclosing that 'Accepted means the request was scheduled, not that Anki has exited,' that native close/save/sync dialogs may cancel it, that callers must retain timer/callback ownership, and that process exit prevents polling a final result. It also declares 'Undo: none' and enumerates possible errors, covering the full risk profile of a destructive lifecycle operation.

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?

Front-loads the core action in the first sentence, then layers the async caveats and metadata in descending importance. The trailing 'Anki-Connect method / Scope / Effect / Completion / Undo / Possible errors' line is somewhat boilerplate but carries real routing and error-handling value, so little is wasted.

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

Completeness5/5

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

With zero params and no output schema, the description carries the entire burden and does so: it explains the asynchronous acceptance semantics, cancellation risk from native dialogs, the absence of undo, and the error set. An agent has everything needed to invoke it and interpret the result correctly.

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

Parameters4/5

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

The tool takes zero parameters and the schema is empty with additionalProperties false, so there is nothing parameter-level to disambiguate. Baseline 4 applies; the description correctly implies no arguments are needed by describing a parameterless lifecycle action.

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?

States a specific verb and resource: 'initiate normal application close after sending the response,' which is unambiguous and clearly distinct from the other application_* siblings (navigate, importFile). The added scope/effect metadata ('Scope: application. Effect: lifecycle') reinforces what is being acted on.

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

Usage Guidelines4/5

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

Explains the trigger context ('Acknowledge a close request, then initiate normal application close') and the ordering constraint (close happens after the response is sent), which tells the agent when this tool is appropriate. It does not name an alternative or an explicit when-not-to-use condition, but no sibling performs an equivalent exit, so the gap is small.

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