Skip to main content
Glama

fetch_due_cards_for_review

Retrieve Anki cards scheduled for review, optionally filtered by deck and due date, for efficient spaced repetition study.

Instructions

Fetch cards due for review, formatted for an LLM to present.

Args:
    deck: Optional[str] - Filter by specific deck name.
    limit: int - Maximum number of cards to fetch (default 5).
    today_only: bool - If true, only fetch cards due today. If false, fetch cards due up to MAX_FUTURE_DAYS ahead (currently {MAX_FUTURE_DAYS}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deckNo
limitNoMax cards to fetch.
today_onlyNoTrue=only today's cards, False=cards due up to MAX_FUTURE_DAYS ahead.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description bears full burden. It explains the today_only behavior and output formatting, but lacks statements on read-only nature, side effects, rate limits, or authentication needs.

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?

Concise, front-loaded with main purpose, then clear argument list. Every sentence adds value; no fluff. Placeholder for MAX_FUTURE_DAYS is efficient.

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?

Good coverage of parameter details and output format. However, lacks context on when to use relative to siblings and missing behavioral traits like idempotency or data source, given no annotations and output schema not shown.

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 67%, but the description adds detail beyond schema (e.g., deck filter as 'specific deck name', today_only with MAX_FUTURE_DAYS). Only minimal repetition of existing schema descriptions.

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?

The name and description clearly state the tool fetches cards due for review, formatted for LLM presentation. It distinguishes from sibling tools like submit_reviews or inspect_cards by specifying its purpose.

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?

Description implies usage for getting cards to review but does not explicitly state when to use versus alternatives, nor does it provide exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samefarrar/mcp-ankiconnect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server