Skip to main content
Glama

add_card

Add a flashcard to an existing deck or create a new deck by providing the deck name, front, and back content. Optionally include tags and hints for organization.

Instructions

Add a flashcard to an existing deck. Creates the deck if it doesn't exist.

Behavior: This tool generates structured output without modifying external systems. Output is deterministic for identical inputs. No side effects. 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. front (str): The front to analyze or process. back (str): The back to analyze or process. tags (str): The tags to analyze or process. hint (str): The hint 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
backYes
hintNo
tagsNo
frontYes
api_keyNo
deck_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. The description claims read-only behavior and no side effects, directly contradicting the tool's mutative nature. While it mentions rate limits and authentication, the core behavioral disclosure is incorrect.

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., behavior repeated). The first sentence is concise, but the rest is verbose and includes irrelevant boilerplate, making it poorly structured.

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

Completeness1/5

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

The tool is relatively simple but the description fails to provide complete context. The output schema exists, but the description's boilerplate about analysis is off-topic and doesn't cover the actual flashcard creation behavior. Key information like idempotency of card addition or error handling for duplicate cards is missing.

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

Parameters1/5

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

Schema coverage is 0%, so description must compensate. For each parameter, it only provides the generic phrase 'to analyze or process', adding no meaningful detail about their purpose, valid values, or format.

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 adds a flashcard to a deck and creates the deck if needed. However, the subsequent description contradicts this by claiming the tool is read-only and generates structured analysis output, creating ambiguity about the actual purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool vs siblings. The 'When to use' section is misleading, suggesting it's for structured analysis/classification, which is irrelevant to flashcard addition.

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