Skip to main content
Glama
anki-workflow-mcp

anki-workflow-mcp

by Gugart43

Manifesto State

manifesto_state

Read the current state of a Manifesto deck, including IDs, topics, taxonomy, catalogs, changelog, queue, or batches, by passing an absolute deck path and optional sections.

Instructions

Read the current state of the Manifesto. deck_dir: absolute path to the deck folder. sections: comma-separated subset to return ('all', 'ids', 'topics', 'taxonomy', 'catalogs', 'changelog', 'queue', 'batches').

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

Input Schema

NameRequiredDescriptionDefault
deck_dirYes
sectionsNoall

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It conveys that this is a read operation ('Read the current state') and enumerates the valid section subsets, but it does not disclose whether state is cached, how errors are handled for invalid section names, or whether the read has any side effects. There is an output schema, so return-format explanation is not required, but other behavioral context is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core purpose, followed by concise parameter definitions. Every sentence earns its place given the 0% schema coverage, and the enumerated section list is necessary rather than wasteful.

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?

The tool is a simple two-parameter read with one required parameter and an output schema. The description covers purpose and both parameters adequately. Remaining gaps—when to prefer this over other read tools and what each section returns—are minor given the output schema and the low complexity.

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 description coverage is 0%, so the description must compensate. It does: deck_dir is defined as an 'absolute path to the deck folder', and sections is described as a 'comma-separated subset' with an explicit list of allowed values. This adds substantial meaning beyond the bare schema, though it does not explain what each section contains or the default 'all' behavior in the text (the schema supplies the default).

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?

The description states a specific verb+resource: 'Read the current state of the Manifesto.' This clearly distinguishes it as a read-only state inspection tool versus sibling mutation tools like manifesto_commit or manifesto_init. However, it does not explicitly contrast with other read tools such as deck_hierarchy_get or id_ledger_query, so it falls short of a 5.

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?

Usage is only implied: an agent can infer it should call this to inspect current state before planning or committing. There is no explicit when-to-use guidance, no exclusions, and no named alternatives. A 3 is appropriate for implied-but-undirected usage.

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