mcp

get_memo_card

Read-onlyIdempotent

Get one flashcard and exactly where it sits in its spaced-repetition cycle: stage, step (consecutive successful recalls), interval, ease, next due date, lapses, its position in the deck's study queue (queue_position of queue_size), and its last 10 reviews. Requires a personal access token with the "memo" scope.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_memo_card"
  }
}

Input Schema

Name	Required	Description
`api_key`	No	Your Datronis personal access token (starts with "dtk_"). Generate one at /app/api-keys/. Required unless sent as an `Authorization: Bearer <token>` HTTP header instead (preferred — see search_jobs' api_key description for why).
`card_id`	Yes	Card id — from list_memo_cards or get_memo_study_queue.
`timezone`	No	The user's IANA timezone, e.g. "Europe/Berlin" or "Asia/Tokyo". Decides what "due today" and "which day" mean. Defaults to UTC — pass it whenever you know it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned review fields (stage, step, interval, ease, next due, lapses, queue position, last 10 reviews) and stating the required "memo" token scope — a real auth constraint not in the annotations.

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?

Front-loaded with the verb and resource, and the field enumeration is dense but earns its place since there is no output schema. The trailing auth sentence is short and useful. Slightly long single sentence but no filler.

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 carries the return-shape burden and does so explicitly, plus it discloses the auth requirement. It omits error behavior for an unknown card_id and any note on why timezone matters, but nothing essential for a correct call is missing.

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 baseline is 3. The description adds no syntax or semantics for card_id, timezone, or api_key beyond what the schema already documents, so it neither compensates nor detracts.

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?

Opens with a specific verb+resource ("Get one flashcard") and immediately scopes it to the spaced-repetition cycle, which cleanly separates it from list_memo_cards, get_memo_study_queue, and review_memo_card. An agent can identify the tool's job without opening the schema.

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: fetch a single card's review state. The description never states when to prefer this over get_memo_study_queue or list_memo_cards, nor any precondition beyond the token scope. Adequate but the routing decision is left to inference.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?