Lexpad – Vocabulary Notebook & Flashcards

Remove a meaning

remove_meaning

Destructive

Removes one meaning, with its examples, from a word, chosen by its position in the word's card. It cannot be undone.

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": {
      "word_id": "<word_id>",
      "meaning_index": "<meaning_index>"
    },
    "name": "remove_meaning"
  }
}

Input Schema

Name	Required	Description	Default
`word_id`	Yes	The id of a word from another tool's result.
`meaning_index`	Yes	Which meaning, counting from 0 in the order get_word lists them.

Output Schema

Name	Required	Description	Default
`id`	Yes
`pos`	No
`level`	No
`topic`	No
`addedOn`	Yes
`headword`	Yes
`meanings`	Yes
`progress`	Yes
`usageNote`	No
`correction`	No
`notebookId`	Yes
`expressions`	No
`collocations`	No
`hardSpelling`	No
`relatedWords`	No
`spellingNote`	No
`pronunciation`	No
`originalMeaning`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses a cascade the annotations do not: the meaning's examples are removed along with it. It also reinforces irreversibility ("cannot be undone"), though that largely echoes destructiveHint=true rather than adding new information.

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?

One sentence plus a short irreversibility warning; the object of deletion and the selection rule are front-loaded and nothing is wasted.

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 annotations covering the safety profile, full schema coverage, and an output schema present, the description covers what an agent needs to invoke it correctly. It omits only edge behavior such as out-of-range index or what happens if the meaning is referenced elsewhere.

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 coverage is 100%, with both word_id and meaning_index fully documented, so the description need not carry parameter meaning. Its phrase "chosen by its position in the word's card" restates the meaning_index documentation without adding format or off-by-one guidance beyond it.

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 (removes) and resource (one meaning, plus its examples) scoped to a word, selected by positional index. It is clearly distinguishable from siblings like delete_word (removes the whole word), update_meaning (modifies in place) and reorder_meanings.

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?

The description implies usage by explaining the selection mechanism (position in the card, as listed by get_word) but never states when to prefer this over update_meaning or delete_word, nor any prerequisite such as confirming with the user first.

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?