Skip to main content
Glama

Get Flashcards

get_flashcards
Read-onlyIdempotent

Get reviewed, evidence-linked episode flashcards with bounded cursor pagination. No scoring or engagement coercion.

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": {
      "slug": "<slug>"
    },
    "name": "get_flashcards"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
operationYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / meta / properties / clip_catalog
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "catalog_id": {
      +      "const": "htrtf-youtube-clips",
      +      "type": "string"
      +    },
      +    "catalog_sha256": {
      +      "pattern": "^[a-f0-9]{64}$",
      +      "type": "string"
      +    },
      +    "catalog_version": {
      +      "maxLength": 80,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "generated_at": {
      +      "format": "date-time",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "catalog_id",
      +    "catalog_version",
      +    "catalog_sha256",
      +    "generated_at"
      +  ],
      +  "type": "object"
      +}
  2. Changed35 schema fields changed
    • removedOutput schema / properties / data / properties / items / items / properties / chapter_id / $ref
      Removed value: -"#/properties/data/properties/items/items/properties/id"
    • addedOutput schema / properties / data / properties / items / items / properties / chapter_id / maxLength
      Added value: +160
    • addedOutput schema / properties / data / properties / items / items / properties / chapter_id / pattern
      Added value: +"^[a-z0-9]+(?:[-.][a-z0-9]+)*$"
    • addedOutput schema / properties / data / properties / items / items / properties / chapter_id / type
      Added value: +"string"
    • addedOutput schema / properties / data / properties / items / items / properties / evidence / items / properties / end_ms / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / data / properties / items / items / properties / evidence / items / properties / start_ms / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / data / properties / total / maximum
      Added value: +9007199254740991
    • removedOutput schema / properties / meta / properties / artifact_manifest_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / artifact_manifest_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / artifact_manifest_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / artifact_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / artifact_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / artifact_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / release_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / release_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / release_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / rights / properties / policy_url / $ref
      Removed value: -"#/properties/meta/properties/canonical_url"
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / format
      Added value: +"uri"
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / maxLength
      Added value: +2048
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / snapshot_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / snapshot_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / snapshot_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / content_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / surface_version / properties / content_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / content_version / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / transcript_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / transcript_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / transcript_version / type
      Added value: +"string"
  3. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful pagination context ('bounded cursor pagination') but omits practical behavior such as the hard page-size ceiling and whether results are ordered or stable across cursors; the 'no scoring or engagement coercion' sentence is vague and adds little operational meaning.

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 compact sentences with the core capability front-loaded, so the reader hits the substance immediately. The closing clause about scoring and engagement coercion is the only low-value sentence and could be dropped without loss.

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?

An output schema exists, so the description need not explain return values, and annotations cover the safety profile. However, with three undocumented parameters at 0% schema coverage, the definition is not complete enough for an agent to page correctly or know the maximum page size without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, so the description carries the full explanatory burden and largely fails it: it never defines what 'slug' identifies, never states the 1-10 limit range or default of 10, and never explains how the cursor is obtained or when iteration ends. Only the word 'pagination' gestures at the cursor parameter, leaving limit and slug semantics undocumented anywhere.

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 names a specific verb and resource ('Get ... episode flashcards') and adds qualifying scope ('reviewed, evidence-linked'), which tells an agent this returns curated flashcard content rather than raw episode data. It does not explicitly contrast with siblings like get_episode or get_clip, so the differentiation is implied by the resource noun rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus get_episode, get_clip, or get_reading_trail, and no prerequisites or exclusions beyond the trailing 'No scoring or engagement coercion' remark, which reads as policy rather than usage direction. An agent must infer that a slug-based lookup of a single episode's flashcards is the intended context.

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