Skip to main content
Glama

Preview an interactive SAT questionnaire

preview_sat_quiz
Read-only

Preview an interactive SAT quiz as one Anki card so students can answer questions, submit for a score, and review explanations without writing to Anki; returns a one-time preview token.

Instructions

Preview one interactive Anki card containing the whole questionnaire. The student can choose answers, submit, see a score, and review explanations. Returns a one-time previewToken and does not write to 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": "preview_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?

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real value on top: it discloses the return value (a one-time previewToken) and that nothing is written to Anki, which explains the non-idempotent hint. It does not state token lifetime/expiry or size limits on the rendered card, which would have made it a 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?

Three short sentences, front-loaded with the core purpose followed by interaction behavior and then the return/no-write disclosure. Nothing is padded, though the middle sentence on student interaction is more about the rendered artifact than about calling the tool.

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?

With no output schema, the description appropriately names what comes back (previewToken) and confirms the no-write side effect. What remains unsaid — whether previews must be committed before expiring, and how this differs from preview_sat_questions — is minor but not negligible.

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% and the nested question/choice structure is documented inline in the schema, so the schema carries the parameter burden. The description adds no meaning about the deck or questions parameters beyond that, which is the expected baseline here.

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 resource: preview one interactive Anki card containing the whole questionnaire, with the interaction flow (choose answers, submit, see score, review explanations) spelled out. It does not distinguish itself from the sibling preview_sat_questions, so an agent must infer the difference, but the purpose itself is unambiguous.

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 only implied: the mention of a one-time previewToken and 'does not write to Anki' suggests a preview-before-commit workflow, presumably preceding commit_sat_preview. There is no explicit statement of when to use this instead of export_sat_quiz or preview_sat_questions, and no exclusions.

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