Skip to main content
Glama

inspect_cards

Inspect Anki card details by card or note ID and selectively retrieve identity, state, scheduling, timestamps, history, or field data.

Instructions

Inspect per-card state with sparse fieldset selection.

Provide EXACTLY ONE of `card_ids` or `note_ids`. When `note_ids` is given,
the tool resolves to all cards belonging to those notes via an `nid:` query.

Use `properties` to pick which categories of information to return. The
default keeps responses small; opt into the heavier categories explicitly.

Property categories:
  - `identity` — cardId, noteId, deck, modelName
  - `state` — suspended, queue, queue_label, type
  - `scheduling` — ease, interval, reps, lapses, raw_due
  - `timestamps` — modified_iso, last_review_iso (the latter only with `history`)
  - `history` — full review log (extra AnkiConnect call). Each entry has
    an ISO timestamp, an "again"/"hard"/"good"/"easy" rating, interval in
    days, and time taken in ms.
  - `fields` — cleaned, non-empty note field content (extra `notesInfo`
    round trip). Image Occlusion notes collapse to a single placeholder.
  - `all` — shorthand for every category above.

Default when `properties` is None: `["identity", "state", "scheduling"]`.

`include_history=True` is kept as a soft-deprecated alias — equivalent to
adding `"history"` to `properties`. Prefer the new param going forward.

Args:
    card_ids: List of card IDs to inspect.
    note_ids: List of note IDs; expands to every card on those notes.
    properties: List of property categories to include.
    include_history: Soft-deprecated alias for `properties=["history", ...]`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idsNo
note_idsNo
propertiesNo
include_historyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It details extra API calls for history and fields, soft-deprecated alias behavior, and note collapse for Image Occlusion. It implicitly indicates read-only nature. No contradictions.

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 well-structured with a purpose statement, constraints, and a bulleted list of property categories. It is slightly lengthy but each part serves a purpose. Front-loaded with key constraint. Good balance.

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?

Given 4 parameters with 0% schema coverage, 13 sibling tools, and an output schema, the description covers all necessary aspects: parameter constraints, defaults, property explanations, behavior for note_ids, and deprecated alias. It does not need to explain return values due to output schema. Complete.

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

Parameters5/5

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

Schema coverage is 0%, so description must compensate. It explains each parameter: exclusive usage of card_ids/note_ids, expansion with note_ids, property categories with explicit list and meanings, and include_history as alias. This adds significant value beyond the bare schema.

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 description clearly states the tool's purpose: 'Inspect per-card state with sparse fieldset selection.' The verb 'inspect' and resource 'per-card state' are specific. The sibling tools include mutations like add_note and search_notes, making this read-only inspection distinct.

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?

The description provides clear usage guidelines: 'Provide EXACTLY ONE of card_ids or note_ids' and explains how note_ids resolves to cards. It defaults properties and notes a deprecated alias. However, it lacks explicit exclusion of alternatives (e.g., when to use search_notes instead).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samefarrar/mcp-ankiconnect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server