Skip to main content
Glama

Save a previewed SAT quiz or flashcard batch to Anki

commit_sat_preview

Saves a previewed SAT quiz or question set to Anki using its one-time preview token, creating the destination deck and quiz note type while skipping duplicates.

Instructions

Save a preview_sat_quiz or preview_sat_questions result. Pass only previewToken. Each token works once, expires after 10 minutes, and is valid only in the server process that issued it. The server skips duplicates and creates the destination deck when needed. An interactive quiz uses a dedicated note type that is created on first use.

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": {
      "previewToken": "<previewToken>"
    },
    "name": "commit_sat_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
previewTokenYespreviewToken returned by preview_sat_questions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: single-use tokens, a 10-minute expiry, server-process affinity, duplicate skipping, automatic deck creation, and a dedicated note type created on first use. These are exactly the operational constraints an agent needs and none are inferable from the structured fields.

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?

Five short sentences, front-loaded with the action and the required parameter, then the constraints in descending priority. No filler or restatement of the title.

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?

Covers the hard parts of a mutating, stateful commit tool: token lifecycle, dedup, deck and note-type creation. With no output schema, it would help to say what comes back (counts, note IDs, or errors on expired/reused tokens), which is the one remaining gap.

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 100%, so the parameter is already documented; the description still adds value by insisting only previewToken be passed and by explaining where the token comes from and how long it lives. It does not describe the expected token format, but the source tool is named.

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?

States a specific verb and resource — save a preview_sat_quiz or preview_sat_questions result — and names the sibling tools that produce the input, so an agent can distinguish it from the preview and export tools without opening the schema.

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

Usage Guidelines4/5

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

"Pass only previewToken" plus "Save a preview_sat_quiz or preview_sat_questions result" makes the prerequisite and sequencing (preview first, then commit) clear. It does not explicitly say what to do on failure or when to re-preview rather than retry, so it stops short of full when/when-not guidance.

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