Lexpad – Vocabulary Notebook & Flashcards

Recent words

get_recent_words

Read-only

Every word in one notebook, or all, in the order it was added, newest first, whatever its progress: new, learning, mastered and paused alike. It takes no filter, search or date range; it answers what the user saved lately. Each word comes with a short form of its meanings, its status and the day it was added. 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_recent_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.5/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, and the description adds genuinely new detail: page size cap, default of 50, total capped at 10000 with totalIsAtLeast, and cursor reuse requiring identical arguments. Its weakest point is that cursor reuse is stated without saying what happens if arguments change. Strong coverage overall for a read tool.

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?

Dense single paragraph, front-loaded with scope and ordering before pagination mechanics. Every sentence adds either selection guidance or behavior an agent needs; nothing is filler.

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?

Covers scope, ordering, return shape, pagination, and count caveats for a 3-parameter read tool with an output schema already documenting returns. An agent has everything needed to call it correctly and interpret paging.

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; the description exceeds it by clarifying cursor round-tripping ('sent back as cursor with the same arguments') and confirming notebook_id accepts 'all' or defaults to the default notebook. It largely restates limit defaults already in the schema, which keeps it from a 5.

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 precisely what the tool returns: every word in one notebook or all, ordered newest first, regardless of progress status. The clause 'It takes no filter, search or date range' implicitly separates it from search_words and other filtered siblings, so an agent can pick correctly without opening schemas.

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 use case ('answers what the user saved lately') and explicitly excludes filtering/search/date-range use, which steers the agent away from this tool for those needs. It stops short of naming the alternative siblings (search_words, get_due_words, list_words) by name, so guidance is strong but not exhaustive.

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?