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

anki-connect-mcp

by SolarianGG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

media.get

media_get
Read-only

Read media bytes as base64.

Instructions

Read media bytes as base64.

A basename is required; no filesystem traversal or arbitrary paths.

Anki-Connect method media.get. Scope: collection. Effect: read. Completion: completed. Undo: none.

Possible errors: collectionUnavailable, internalError, invalidParams, notFound, staleSession.

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": {
      "filename": "<filename>"
    },
    "name": "media_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoOptional. Collection session ID: the `session` field returned by `collection_get`. Usually omit it — the server then uses the session current at the time of the call. Pass it to make the call fail with `staleSession` instead of acting on a different profile/collection than the one your IDs, cursors and tokens came from.
filenameYesMedia file basename to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description is not obligated to re-establish it. It still adds real context: the backing Anki-Connect method, collection scope, "Undo: none", and an enumerated error set (collectionUnavailable, internalError, invalidParams, notFound, staleSession) that tells the agent exactly which failure modes to handle. It stops short of describing payload size limits or truncation behavior for large media.

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-loaded with the one thing that matters (what it returns), followed by compact labeled metadata lines that scan quickly. Minor waste: "Effect: read" duplicates readOnlyHint=true and could be dropped.

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 two-parameter read with no output schema, the definition covers encoding of the result, path restrictions, scope, and error taxonomy, which is most of what an agent needs. The remaining gap — nothing about response size or how large files are handled — is modest for a tool of this complexity.

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 both `session` and `filename` are already well documented, including the staleSession rationale. The description's "basename is required; no filesystem traversal or arbitrary paths" merely restates the pattern and `not` enum constraints already encoded in the schema, adding rationale but no new semantics. Baseline 3 applies when the schema does the heavy lifting.

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?

"Read media bytes as base64" gives a specific verb, a specific resource, and even the return encoding, which immediately separates it from siblings like media_list, media_getDirectory, media_store and media_delete. An agent can pick this tool without opening the schema.

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 purpose implies the use case (fetch the content of one known media file), and the basename-only constraint hints at when this tool is not appropriate. However, no sibling is named as the alternative for directory listings or bulk enumeration, and no preconditions (e.g. collection availability or session handling) are given beyond the error list.

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