Skip to main content
Glama

Export a fillable SAT quiz as HTML

export_sat_quiz

Save SAT multiple-choice questions as an offline interactive questionnaire that lets users select answers, submit for a score, and review explanations without altering Anki.

Instructions

Save a self-contained interactive questionnaire. Open the file in any modern browser to choose answers, submit, see a score and review explanations. Works offline and does not change Anki.

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_quiz"
  }
}

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?

With annotations supplied, the description still adds real behavioral context: the output is a single self-contained file, it works offline, and it does not modify the Anki collection. That last point is valuable because readOnlyHint=false means something is written (a file), and the description clarifies what is and is not mutated. Remaining gaps are idempotency/overwrite behavior and whether the deck must already exist, which the annotations and schema do not fully settle.

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?

Three short sentences, front-loaded with the action and output, then user-facing behavior, then the side-effect guarantee. No sentence is redundant or padded.

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?

The tool is simple (two required params, fully documented schema, no nested objects), but there is no output schema, so the agent gets no information about what is returned — presumably a file path — nor where the file is written. For an export tool whose whole purpose is producing an artifact, that omission leaves a meaningful gap.

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?

Schema description coverage is 100%, so both 'deck' and 'questions' (including the A–D choice structure, answer enum, and explanation field) are already documented in the schema. The description adds nothing about parameter meaning, so the baseline 3 applies.

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 concrete action and output: save a self-contained interactive questionnaire that opens in a browser, scores answers, and shows explanations. That is specific enough to separate it from commit_sat_preview (mutates Anki) and preview_sat_quiz, though it never names the closest sibling, export_sat_tsv, so the format distinction (HTML vs TSV) is only implied by the title.

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?

Usage is implied rather than stated: if the user wants an offline, interactive artifact, use this; the note that it 'does not change Anki' hints at the boundary with committing tools. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the routing from sibling names alone.

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