Skip to main content
Glama
anki-workflow-mcp

anki-workflow-mcp

by Gugart43

Manifesto Import

manifesto_import

Imports a legacy manifesto.md file and converts it into manifesto.json, parsing markdown sections and reporting any parsing issues for Anki deck workflows.

Instructions

Import a legacy manifesto.md into manifesto.json format. Parses the markdown file and creates manifesto.json. deck_dir: folder containing the manifesto.md. manifesto_md_name: filename (default 'manifesto.md'). Reports all parsed sections and any parsing issues.

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": {
      "deck_dir": "<deck_dir>"
    },
    "name": "manifesto_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
deck_dirYes
manifesto_md_nameNomanifesto.md

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations at all, so the description carries the full behavioral burden. It discloses that parsing issues are reported and that manifesto.json is created, but it never says whether an existing manifesto.json is overwritten, what happens on parse failure (partial write vs abort), or whether the operation is idempotent - critical for a tool that writes a file.

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 action and target format, then parameters. The sentence 'Parses the markdown file and creates manifesto.json' is largely redundant with the opening sentence, which is the only real waste.

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 not be explained, and the tool is only two parameters deep. Still, for a file-writing import tool with zero annotations, the absence of overwrite/failure semantics leaves a meaningful gap for correct invocation.

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?

Schema coverage is 0%, so the description must carry parameters, and it does: deck_dir is 'folder containing the manifesto.md' and manifesto_md_name is the filename with default 'manifesto.md'. Both parameters gain meaning beyond their bare types, though path format or relative-vs-absolute expectations are unstated.

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 resource: 'Import a legacy manifesto.md into manifesto.json format', with a concrete transformation described. It doesn't name or differentiate against nearby siblings like manifesto_init or manifesto_commit, so an agent must infer the boundary from names alone.

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 word 'legacy' implies the migration use case, which is useful implied context. But there is no explicit statement of when to use this versus manifesto_init, nor any exclusion such as when manifesto.json already exists or when the markdown is not in legacy format.

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