Skip to main content
Glama

Export individual SAT flashcards for Anki

export_sat_tsv

Exports SAT multiple-choice questions to an import-ready TSV with deck, styled Q&A cards, and tags without AnkiConnect or changing your Anki collection; returns the file path.

Instructions

Save an import-ready TSV with the requested deck, styled question and answer cards, and tags. Works without AnkiConnect and does not change the Anki collection. Returns the file path.

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": "<deck>",
      "questions": "<questions>"
    },
    "name": "export_sat_tsv"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesDeck for the notes. If the deck is missing, commit_sat_preview creates it when at least one question is new.
questionsYesOne to fifty SAT multiple-choice questions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real value by disclosing that this writes a file without touching the Anki collection and that it requires no AnkiConnect. That resolves the apparent tension between 'save' and 'does not change the collection.' It omits where the file lands, overwrite behavior, and silence on the idempotentHint=false implication, keeping it below 5.

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 sentences, front-loaded with the artifact produced, followed by the behavioral caveat and return value. No filler; 'styled question and answer cards' is slightly vague but functional.

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?

For a two-parameter tool with full schema coverage and no output schema, the description gives what an agent needs: what is produced, that it is side-effect-free on the collection, and that a file path is returned. Missing only destination/overwrite details and any note that tags and card styling are derived rather than supplied.

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

Parameters3/5

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

With 100% schema description coverage, the schema already carries full parameter meaning, so the baseline is 3. The description only echoes 'requested deck' and adds a 'tags' element that is not present as an input parameter, contributing no syntax or format detail beyond the schema.

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 and artifact — saving an import-ready TSV containing deck, styled question/answer cards — which is clearly distinct from the quiz-export and commit siblings. It stops short of naming a sibling or the condition that selects this one over export_sat_quiz, so it is clear but not differentiating.

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?

The phrase 'Works without AnkiConnect and does not change the Anki collection' implicitly positions this as the offline alternative to the commit path, but the guidance is inferential rather than explicit. There is no stated when-to-use vs export_sat_quiz, and no prerequisites or follow-up step (import into Anki) spelled out.

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