Skip to main content
Glama

Study pack for any topic: flashcards, quiz, review plan (8 credits or $0.040)

make_study_pack
Read-onlyIdempotent

A topic in, a ready-to-teach pack out: summary, key points, 4-20 flashcards, a 3-12 question multiple-choice quiz with explanations and a balanced answer key, common misconceptions, a 30-day spaced review plan, an Anki import file and a printable worksheet, in 14 languages. PAID: 8 Iris Credits with a credits key (Authorization: Bearer iris_... header or the key argument; packs from $0.25, buyable with a plain USDC transfer, see payment_options), or $0.040 per call with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo). An unpaid call returns the payment terms and charges nothing; bad input is rejected first; failed work is never charged (credits are refunded). Same result as GET /v1/study/pack.

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": {
      "topic": "<topic>"
    },
    "name": "make_study_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional Iris Credits key (iris_ + 48 hex). Better: set it once as the MCP header Authorization: Bearer <key>. Without a key the call is paid with x402 / MPP over MCP.
langNoLanguage of the whole pack. Default en.
cardsNoNumber of flashcards 4-20, default 10.
levelNoAudience level. Default intermediate.
topicYesWhat to study, 2-120 characters (e.g. "the French Revolution", "Python list comprehensions", "IELTS cohesive devices"). Default: photosynthesis (demo).
questionsNoNumber of quiz questions 3-12, default 6.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, but the description adds substantial behavioral context beyond them. It discloses pricing, accepted authorization methods, unpaid-call behavior, input validation ordering, and the no-charge/refund policy for failed work.

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?

The purpose and output list are front-loaded, so an agent gets the core capability immediately. The payment sentence is dense and repeats some range information already in the schema, but most clauses cover material behavior for a paid tool.

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

Completeness5/5

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

For a paid content-generation tool with no output schema, the description lists all major returned artifacts, language support, payment paths, validation order, and refund behavior. This is enough for an agent to select and invoke the tool correctly.

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 the schema already documents the topic, language, level, card count, question count, and key parameters. The description repeats the flashcard and question ranges and mentions 14 languages, but it does not add parameter semantics beyond what the schema already provides.

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?

The opening sentence names the input and enumerates the exact artifacts returned, including summary, key points, flashcards, quiz, misconceptions, review plan, Anki file, and worksheet. This clearly distinguishes it as a study-pack generator rather than a payment or text-analysis sibling.

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 description gives detailed invocation context for paid calls and points to payment_options for buying credit packs, but it does not explicitly state when to choose this tool over other content-generation siblings or when not to use it. Usage is largely implied by the output list and payment mechanics.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources