Skip to main content
Glama
anki-workflow-mcp

anki-workflow-mcp

by Gugart43

Media Figure Build

media_figure_build

Build a standardized AnkiMBR figure or table tag with clinical caption, optional title, and context link to connect media to the card's concept without inline styles.

Instructions

Construct a standardized AnkiMBR tag with clinical caption. Ensures semantic container formatting (class='anki-figure') without inline styles. Supports optional title and context_link to connect the image/table to the card's clinical concept.

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_figure_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
titleNo
captionNo
filenameYes
item_typeNofigure
context_linkNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. It does disclose real behavioral traits: the output uses a semantic container class and deliberately omits inline styles, and title/context_link are optional. It never states whether the tool is a pure formatter with no side effects, whether it validates the filename, or what happens when caption is empty.

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?

Three short sentences, front-loaded with the effect and followed by the formatting constraint and optional fields. No filler; only the unexplained "style" leaves a dangling reference.

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

Completeness3/5

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

An output schema exists, so return values need no prose. However, with six parameters at 0% schema description coverage and no annotations, the description should cover the remaining fields (style, item_type, filename form) and at least assert the tool is side-effect free for building a string.

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 0% across six parameters, so the description must compensate. It explains caption as a "clinical caption" and context_link as tying the image/table to the card's clinical concept, which adds meaning beyond the names. It leaves style entirely unexplained and only hints at item_type ("image/table") and filename requirements.

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?

States a specific verb and artifact: "Construct a standardized AnkiMBR <figure> tag with clinical caption," plus the output constraint (class='anki-figure', no inline styles). An agent knows exactly what is produced, though nothing distinguishes it from the sibling table_build even though item_type supports "table".

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 when-to-use guidance, no prerequisites (e.g., whether the referenced image must already exist or be registered via image_sync/image_namespace), and no exclusions or named alternatives. The agent must infer the call context entirely from the tool name.

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