Skip to main content
Glama

Axad

Cards to review

due_cards
Read-only

List the learner's flash cards that are due for review now, the most overdue first, each with an example sentence. lang limits it to one language and limit (1 to 20, default 10) caps the number. Returns the cards and the total due.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "due_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive and non-open-world, so safety is covered. The description adds genuine behavior beyond that: the ordering guarantee, the fact that each card carries an example sentence, and that the response includes both the cards and the total due count.

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: purpose and ordering first, parameter constraints second, return shape last. No redundant phrasing and nothing buried.

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 usefully states what comes back (cards plus total due) and what each card includes. Minor gaps remain — the other card fields and whether 'now' is evaluated server-side — but nothing critical for correct invocation is missing.

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 0%, so the description carries the burden and mostly does: 'lang limits it to one language' gives meaning beyond the bare string type, and the limit range/default is restated. It does not explain what happens when lang is omitted (mixed languages?), which is the one real ambiguity.

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?

The description gives a specific verb and resource — 'List the learner's flash cards that are due for review now' — plus a deterministic ordering ('most overdue first'). That is enough to distinguish it from review_card or browse_catalog, though no sibling is named explicitly.

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?

'Due for review now' implies the usage context, and the result is plainly a queue to feed into a review flow. However, it never says when to prefer this over review_card or how the returned cards should be acted upon, leaving the agent to infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.