Skip to main content
Glama

list_cards

Read-only

Read complete cards and editable sources, with formatting and authenticated media URLs. GET media URLs with the same connector Bearer token; do not speak URLs or markup. Source contains cloze answers: use study tools when quizzing. Shared source edits affect sibling_card_ids. Results are newest first; follow next_cursor as before_card_id while has_more. Default limit 50, max 500; a page of large cards may hold fewer than limit, so trust has_more, not the count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deckNoFilter to one deck by name.
limitNo
searchNoSubstring search over fronts and backs.
before_card_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYes
has_moreYes
next_cursorNo
total_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / properties / before_card_id
      Added value: +{
      +  "format": "int64",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • removedOutput schema / $defs / CardOut / properties / back
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / $defs / CardOut / properties / back_html
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / $defs / CardOut / properties / cloze_index
      Added value: +{
      +  "format": "uint32",
      +  "minimum": 0,
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / $defs / CardOut / properties / deck_id
      Added value: +{
      +  "format": "int64",
      +  "type": "integer"
      +}
    • removedOutput schema / $defs / CardOut / properties / front
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / $defs / CardOut / properties / front_html
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / $defs / CardOut / properties / media
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/MediaOut"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / $defs / CardOut / properties / ord
      Added value: +{
      +  "format": "uint32",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / $defs / CardOut / properties / source
      Added value: +{
      +  "$ref": "#/$defs/SourceOut"
      +}
    • removedOutput schema / $defs / CardOut / properties / tags
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / $defs / CardOut / properties / type_answer
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / $defs / CardOut / required
      Previous value: -[
      -  "card_id",
      -  "front",
      -  "back",
      -  "tags"
      -]New value: +[
      +  "card_id",
      +  "deck_id",
      +  "ord",
      +  "front_html",
      +  "back_html",
      +  "source",
      +  "media"
      +]
    • addedOutput schema / $defs / MediaOut
      Added value: +{
      +  "properties": {
      +    "filename": {
      +      "type": "string"
      +    },
      +    "media_id": {
      +      "format": "int64",
      +      "type": "integer"
      +    },
      +    "mime": {
      +      "type": "string"
      +    },
      +    "size": {
      +      "format": "uint64",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "media_id",
      +    "url",
      +    "mime",
      +    "filename",
      +    "size"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / $defs / SourceOut
      Added value: +{
      +  "properties": {
      +    "back_html": {
      +      "type": "string"
      +    },
      +    "front_html": {
      +      "type": "string"
      +    },
      +    "note_id": {
      +      "format": "int64",
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "note_type": {
      +      "type": "string"
      +    },
      +    "read_only_reason": {
      +      "description": "Non-null when a legacy import lacks a lossless editable source.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "sibling_card_ids": {
      +      "items": {
      +        "format": "int64",
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    "tags": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "note_type",
      +    "front_html",
      +    "back_html",
      +    "tags",
      +    "sibling_card_ids"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / has_more
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / next_cursor
      Added value: +{
      +  "format": "int64",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / total_count
      Added value: +{
      +  "format": "uint32",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "cards"
      -]New value: +[
      +  "cards",
      +  "total_count",
      +  "has_more"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive, and the description adds substantial operational context: authenticated media URL retrieval with the same Bearer token, an instruction not to speak URLs or markup, a warning that sources contain cloze answers, a note that shared source edits affect sibling_card_ids, and pagination behavior. This is well beyond what the annotations provide.

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 description is dense but front-loads the core purpose and then packs pagination, media auth, and cloze caveats efficiently. Every sentence carries relevant information, though the semicolon-heavy style is slightly hard to parse.

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?

An output schema exists, so return values need not be explained. For a list tool with pagination, media authentication, and cloze-answer considerations, the description covers the necessary behavioral and parameter context without obvious gaps.

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 50%, with 'deck' and 'search' described in the schema but 'limit' and 'before_card_id' left undocumented there. The description compensates by explaining limit defaults and maximums and by linking before_card_id to next_cursor/has_more pagination, though it could state before_card_id's role more directly.

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 ('Read') and resource ('complete cards and editable sources') with scope details (formatting, authenticated media URLs). It explicitly routes quizzing use cases to study tools, making it distinguishable from siblings like show_answer and panel_grade.

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?

Provides clear context for when to use it versus study tools ('use study tools when quizzing') and notes the Bearer token requirement for media URLs. However, it doesn't name specific alternative tools for listing or filtering, leaving some routing inference to the agent.

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.