Lexpad – Vocabulary Notebook & Flashcards

Lexpad help

lexpad_help

Read-only

Answers questions about Lexpad itself from Lexpad's own public pages: what it can do, how to do something in the app, platforms and downloads, privacy, plans, prices and allowances, and what changed lately. A search returns up to 4 short passages, each with the lexpad.app page it comes from. Topic plans adds the AI card and Lex allowances, the trial length and, outside ChatGPT, the prices in force right now; topic whats_new returns the newest changes with their dates. found is false when the pages say nothing about it. The content follows the website, so it covers features added after this tool was listed.

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

Input Schema

Name	Required	Description
`limit`	No	With whats_new: how many changes, 1 to 10. Default 5.
`query`	No	The question about Lexpad, in English, e.g. how do I import words from a Kindle.
`topic`	No	search (the default), plans for prices and allowances, or whats_new for recent changes.

Output Schema

Name	Required	Description	Default
`found`	Yes
`plans`	No
`source`	Yes
`changes`	No
`install`	No
`passages`	No
`fetchedAt`	Yes
`suggestion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedOutput schema / properties / install

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "device": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "device",
+      "name",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / suggestion

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "links": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "device": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "device",
+          "name",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "surface": {
+      "type": "string"
+    },
+    "why": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "surface",
+    "name",
+    "why",
+    "links"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

Changed2 schema fields changedNov 1, 2026

addedOutput schema / properties / plans / properties / dailyCeiling

Added value: +{
+  "type": [
+    "null",
+    "integer"
+  ]
+}

addedOutput schema / properties / plans / properties / surfaces

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "counts": {
+        "type": "string"
+      },
+      "freePerDay": {
+        "type": "integer"
+      },
+      "proPerDay": {
+        "type": [
+          "null",
+          "integer"
+        ]
+      },
+      "proUnlimited": {
+        "type": "boolean"
+      },
+      "surface": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "surface",
+      "counts",
+      "freePerDay"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

AddedOct 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only and non-destructive annotations, it discloses the public-page source, the four-passage search limit, page attribution for passages, the found=false no-information behavior, and website-driven content freshness. It also explains current-price and dated-change behavior for the specialized topics.

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?

The description front-loads its purpose and scope, then efficiently covers results, topic-specific behavior, empty results, and freshness. The sentences are dense but contain no filler or redundant restatement of the title.

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?

Together with the fully documented three-parameter schema, annotations, and output schema, the description supplies the source boundaries, mode selection, result expectations, and freshness needed for correct invocation. The absence of explicit sibling exclusions is a minor selection-guidance gap rather than missing operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents all parameters, the description substantially expands the topic enum's meaning: plans includes the AI card, Lex allowances, trial length, and a platform-specific price caveat, while whats_new returns dated changes. It also clarifies the result behavior associated with the default search mode rather than merely repeating schema text.

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 clearly states that the tool answers questions about Lexpad itself using Lexpad's public pages, then enumerates supported subjects such as app usage, downloads, privacy, plans, and recent changes. This meta-help scope distinguishes it from siblings that manage or query the user's words and notebooks.

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 usage contexts for general searches, pricing and allowance questions through plans, and recent-change questions through whats_new. It does not explicitly state when not to use it or route agents to siblings such as search_words for vocabulary queries or send_feedback for feedback.

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?