Skip to main content
Glama
Sign In

mcp

by com.datronis
OverviewDiscussionsAdmin

update_memo_card

Idempotent

Edit a flashcard's front, back, hint or tags. Only fields you pass change; the card keeps its review schedule. 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": "update_memo_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
backNoMarkdown is rendered on both the web app and the study flashcard: **bold**, _italic_, ~~strike~~, `code`, bullet/numbered lists, > quotes, and [links](url). A single newline renders as a line break (no need for a blank line between lines of the same side).
hintNoEmpty string removes the hint. Markdown is rendered on both the web app and the study flashcard: **bold**, _italic_, ~~strike~~, `code`, bullet/numbered lists, > quotes, and [links](url). A single newline renders as a line break (no need for a blank line between lines of the same side).
tagsNoReplaces the whole tag list.
frontNoMarkdown is rendered on both the web app and the study flashcard: **bold**, _italic_, ~~strike~~, `code`, bullet/numbered lists, > quotes, and [links](url). A single newline renders as a line break (no need for a blank line between lines of the same side).
api_keyNoYour 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_idYesCard to edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / back / description
      Added value: +"Markdown is rendered on both the web app and the study flashcard: **bold**, _italic_, ~~strike~~, `code`, bullet/numbered lists, > quotes, and [links](url). A single newline renders as a line break (no need for a blank line between lines of the same side)."
    • addedInput schema / properties / front / description
      Added value: +"Markdown is rendered on both the web app and the study flashcard: **bold**, _italic_, ~~strike~~, `code`, bullet/numbered lists, > quotes, and [links](url). A single newline renders as a line break (no need for a blank line between lines of the same side)."
    • changedInput schema / properties / hint / description
      Previous value: -"Empty string removes the hint."New value: +"Empty string removes the hint. Markdown is rendered on both the web app and the study flashcard: **bold**, _italic_, ~~strike~~, `code`, bullet/numbered lists, > quotes, and [links](url). A single newline renders as a line break (no need for a blank line between lines of the same side)."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: partial-update semantics ('only fields you pass change') and the guarantee that review scheduling data is untouched, plus the auth scope requirement. It stops short of describing the response or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and affected fields, followed by update semantics and then the auth requirement. No filler, no repetition of the title, nothing to cut.

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?

For a 6-parameter mutation tool with no output schema and decent annotations, the description covers scope, partial-update behavior, preservation of review history, and auth. It is close to complete; the only gap is that with no output schema present it could hint at what a successful call returns.

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 100%, so the baseline is 3, but the description adds real meaning the schema does not: 'Only fields you pass change' clarifies PATCH-style optionality for the five non-required fields. It reinforces rather than merely restates the field list, though it adds nothing about individual parameter formats.

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?

Names a specific verb (Edit) and resource (flashcard) and enumerates exactly which fields are editable (front, back, hint, tags), which implicitly separates it from add_memo_cards and update_memo_deck. It never explicitly names a sibling or states the contrast, so it falls just short of the 5 bar.

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 implied rather than stated: the field list and 'card keeps its review schedule' make it obvious this is for modifying an existing card. There is no explicit when-to-use versus add_memo_cards or update_memo_deck, no prerequisites beyond the token scope, and no exclusions.

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

All mcp toolsInspect
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