Skip to main content
Glama
CSOAI-ORG

Flashcard AI MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python

quiz_session

Begin a quiz from selected deck in standard, reverse, or mixed modes. Reviews due cards using SM-2 spaced repetition scheduling.

Instructions

Start a quiz session from a deck. Modes: standard (front->back), reverse (back->front), mixed. Returns cards due for review with SM-2 scheduling.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: deck_name (str): The deck name to analyze or process. count (int): The count to analyze or process. mode (str): The mode to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNostandard
countNo
api_keyNo
deck_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

C2.3/5.0
Behavior2/5

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

The description claims the tool is read-only and stateless, but starting a quiz session and returning cards due for review based on SM-2 scheduling implies state dependence. This internal contradiction undermines transparency. Rate limits and error handling are provided but are generic and not verified for this specific tool.

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

Conciseness2/5

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

The description is overly long with redundant sections (e.g., repeating 'Behavioral Transparency' in a separate block). The first sentence is concise, but the rest dilutes clarity with generic text that could be omitted.

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

Completeness2/5

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

Despite having an output schema, the description fails to explain core behavior like what 'starting a session' means, how scheduling works, or how the tool interacts with the deck. The generic sections do not add value and leave important 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?

With 0% schema coverage, the description should compensate but uses generic phrases like 'The deck name to analyze or process'. Only the mode parameter benefits from the description listing values (standard, reverse, mixed). Other parameters lack meaningful context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence clearly states the tool starts a quiz session from a deck with modes and returns cards due for review. However, the description then pivots to generic language about 'structured analysis or classification', which obfuscates the tool's actual purpose and may mislead an AI agent.

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?

The 'When to use' and 'When NOT to use' sections are generic and irrelevant to quiz sessions, suggesting use for 'structured analysis' rather than quizzing. No guidance is provided on when to choose this tool over siblings like add_card or get_stats.

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/CSOAI-ORG/flashcard-ai-mcp'

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