Skip to main content
Glama

Nibomo

by com.nibomo
OverviewDiscussionsAdmin

Next flashcard question

next_review_card
Read-onlyIdempotent

Returns the next card to review (cardId, frontText, no answer) in app queue order: due cards reviewed within an hour, other due cards, then new. card:null: nothing due in that selection (all cards when unfiltered); tell nextDueAt in the learner's timezone (null: none scheduled), don't re-call, and offer adding cards or ungraded practice (get_guide(study)).

Input Schema

NameRequiredDescriptionDefault
tagsNoMatch any existing workspace tag, case-insensitively. Unknown tags return 400; [] matches nothing. Cannot combine with deckId.
deckIdNoSaved deck UUID (tag filter); no deck tags means all cards. Cannot combine with tags.
workspaceIdNoWorkspace UUID; omit for selected. Keep fixed through review/retries.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / data / properties / nextDueAt
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / data / required
      Previous value: -[
-  "workspaceId",
-  "card"
-]New value: +[
+  "workspaceId",
+  "card",
+  "nextDueAt"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses queue ordering, that no answer is included, null semantics, nextDueAt timezone handling, and a do-not-recall behavior. This is rich behavioral context that helps an agent invoke and follow up correctly.

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-loaded with the main return behavior, then null handling and follow-up guidance. It is appropriately sized, though the shorthand 'card:null' and parenthetical callout reduce readability slightly.

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?

Given rich schema coverage, annotations, and an output schema, the description is largely complete: it explains null results, nextDueAt, and not re-calling. It could better connect a successful card return to the reveal_answer and submit_review workflow.

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 input schema already documents tags, deckId, and workspaceId in detail. The description adds only a light reference to 'unfiltered' selection and does not meaningfully extend parameter semantics.

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 states a specific verb and resource: returns the next review card, including cardId and frontText, explicitly without the answer. It also defines queue order and distinguishes the returned payload from a reveal-answer operation.

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?

It gives clear guidance for the null case: tell nextDueAt, don't re-call, and offer adding cards or ungraded practice via get_guide(study). It does not explicitly state when to move to reveal_answer or submit_review, so sibling workflow guidance is incomplete.

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

All Nibomo 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