anki-workflow-mcp

Overview Schema Source Related Servers Discussions Admin

Manifesto Plan Set

manifesto_plan_set

Registers a top-down total card budget plan in the Manifesto before drafting, enforcing that total card quantities are set and chunked into batches of 20 for controlled production.

Instructions

Register the top-down total card budget plan for a topic into the Manifesto before drafting. Enforces that the TOTAL quantity of cards is planned before complete production, chunked strictly into batches of 20 (MAX_BATCH = 20).

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>",
      "total_planned": "<total_planned>",
      "batches_planned": "<batches_planned>"
    },
    "name": "manifesto_plan_set"
  }
}

Input Schema

Name	Required	Default
`deck_dir`	Yes
`rationale`	No
`batch_size`	No
`total_planned`	Yes
`breakdown_json`	No	{}
`batches_planned`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuine behavioral gate: the total must be planned up front and work is chunked strictly into batches of 20 (MAX_BATCH = 20). It says nothing about idempotency, overwrite behavior on re-registration, error modes, or permissions, which matters for a state-writing tool.

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?

Two dense sentences with the constraint front-loaded and no filler. The MAX_BATCH restatement is slightly redundant but serves as emphasis of the hard limit.

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 batching rule is covered. But for a six-parameter write tool with no annotations and zero schema coverage, the missing parameter meaning and lack of failure/overwrite behavior leave real gaps.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate and largely does not. It clarifies total_planned ('TOTAL quantity of cards') and the batch constraint, but deck_dir, rationale, breakdown_json, and the format of batches_planned are entirely undefined in both schema and description.

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: 'Register the top-down total card budget plan for a topic into the Manifesto'. The 'before drafting' clause hints at its place in the pipeline relative to production tools, though it never names a sibling such as topic_budget_plan or manifesto_commit to differentiate.

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?

'before drafting' and 'before complete production' imply a sequencing requirement, which is real usage guidance. However there is no explicit statement of when to prefer this over topic_budget_plan, what happens if called twice, or any precondition that must hold, so the agent must infer the routing.

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

Deploy Server