Skip to main content
Glama
Sign In

mcp

by com.datronis
OverviewDiscussionsAdmin

create_memo_deck

Create a new Memo flashcard deck, optionally with its first cards (up to 200). For language learning set front_lang/back_lang (BCP-47, e.g. "es-ES" / "en-US") so the user hears correct free text-to-speech in the browser. 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": {
      "title": "<title>"
    },
    "name": "create_memo_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoOne emoji, e.g. "๐Ÿ‡ฏ๐Ÿ‡ต". Defaults to ๐Ÿ“š.
cardsNoOptional cards to add right away (up to 200; use add_memo_cards for more).
colorNoHex color, e.g. "#6366f1".
titleYesDeck name, e.g. "Japanese N5 vocabulary".
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).
back_langNoBCP-47 language of the BACK side, e.g. "en-US". Omit to auto-detect.
front_langNoBCP-47 language of the FRONT side, e.g. "ja-JP" โ€” used for free in-browser text-to-speech. Omit to auto-detect.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / cards / items / properties / back / description
      Previous value: -"Answer side โ€” e.g. the translation or answer."New value: +"Answer side โ€” e.g. the translation or answer. 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 / cards / items / properties / front / description
      Previous value: -"Prompt side โ€” e.g. a word in the language being learned, or a question."New value: +"Prompt side โ€” e.g. a word in the language being learned, or a question. 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 / cards / items / properties / hint / description
      Previous value: -"Optional clue shown before the answer is revealed."New value: +"Optional clue shown before the answer is revealed. 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

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (not read-only, non-destructive, non-idempotent), so the bar is lower. The description adds genuinely new context: the required personal access token scope ("memo") and the fact that language tags drive free browser text-to-speech โ€” auth and side-effect behavior not present 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?

Three sentences, all front-loaded with the core action first, then the optional-card count, then the language/TTS rationale and auth prerequisite. Dense but each sentence earns its place; the lang sentence is slightly packed.

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 an 8-param creation tool with no output schema, the description covers the action, the optional bulk payload, the auth requirement, and the main language-learning use case. It does not state what the call returns (e.g. deck id), which is a modest gap but the schema covers the parameter-level detail.

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 high (88%), so the baseline is 3, but the description adds rationale beyond the schema for front_lang/back_lang (BCP-47, TTS pronunciation benefits). The only gap is that it explains no other parameter (icon, color, description) beyond what the schema already documents.

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 and resource ("Create a new Memo flashcard deck") and scopes the optional initial card creation ("up to 200"), which implicitly distinguishes it from add_memo_cards. An agent can tell what it produces and what it also does 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 Guidelines4/5

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

Gives a clear conditional: set front_lang/back_lang for language learning so browser TTS is correct, otherwise omit. It stops short of naming add_memo_cards as the follow-up alternative for larger batches (that lives only in the schema), so it is clear context rather than full when-not guidance.

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