Lexpad – Vocabulary Notebook & Flashcards

Words due today

get_due_words

Read-only

The words waiting for review today: due today or overdue, by the date in the user's own timezone, in one notebook or all. Paused words and words not yet practised are left out. Newest added first. It takes no filter, search or sort, so it is the ready-made review list. Each word comes with a short form of its meanings, its box and its due date. Up to 100 words a page (default 50). The first page gives total, the number of matching words, counted up to 10000 (totalIsAtLeast marks a larger count). While more remain, a page ends with next_cursor; sent back as cursor with the same arguments, it returns the next page.

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": "get_due_words"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Words per page, 1 to 100. Default 50.
`cursor`	No	next_cursor from the previous page; omit for the first page.
`notebook_id`	No	A notebook id from list_notebooks, or all. Omit for the default notebook.

Output Schema

Name	Required	Description	Default
`total`	No
`words`	Yes
`nextCursor`	No
`notebookId`	Yes
`totalIsAtLeast`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the safety annotations, the description discloses the exclusion rules, the sort order (newest added first), the page size and default, the capped counting (10000, flagged by totalIsAtLeast) and the cursor contract. That is a lot of real behavioural detail that an agent could not infer from the hints alone.

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?

It is long, but the scope and exclusions come first, and later sentences cover ordering, page size, totals and cursoring, each of which carries information. Some phrasing repeats the schema (limit and cursor), which keeps it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers filtering rules, ordering, pagination, counting limits and result shape, so it is complete for a paginated read tool. Because an output schema exists, return-value detail is only a bonus.

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 already 100%, so the schema carries the heavy lifting, but the description still adds meaning: 100 per page with a default of 50, and the rule that the cursor must be sent back with the same arguments. The notebook scope ('one notebook or all') is also clarified in prose.

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 opening clause names the specific resource and its precise scope: words due today or overdue, in the user's own timezone, in one notebook or all. That scope is enough to separate it from list_words, get_recent_words and search_words without opening any 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?

It sets out the exclusions clearly (paused words and words not yet practised are left out) and gives the condition that selects it over the filtering siblings: it takes no filter, search or sort, so it is the ready-made review list. Those siblings are only implied rather than named, so the routing is a little weaker than an explicit alternative.

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

All Lexpad – Vocabulary Notebook & Flashcards 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?