get_docFetch the canonical Markdown source of a page. Public and unlisted pages are open to anyone; private pages require the owner's lp_ API key.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The document slug — the path part of its https://lucid.page/<slug> URL. |
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| markdown | Yes | The canonical Markdown source of the page |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context about authentication and access levels, which is not available in the annotations or schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact sentences: the first states the core function, the second covers access constraints. No filler or redundant restatement of the tool name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter read tool with an output schema and robust annotations, the description covers the essential operational details: what is fetched, which pages are accessible, and what credential is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage for the single parameter, including a helpful description of what the slug is. The tool description adds no additional parameter information, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Fetch the canonical Markdown source of a page.' This unambiguously distinguishes get_doc from siblings like list_docs, update_doc, and delete_doc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context about when access is permitted (public/unlisted vs. private) and the auth requirement for private pages. It does not explicitly name alternatives, but the access rules make the tool's role evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource-action pair: doc CRUD, bundle creation, listing, and account limits. get_doc vs list_docs clearly separates single-fetch from collection listing, and publish/update/delete/are unambiguous.
All tools follow a consistent snake_case verb_noun pattern: create_bundle, delete_doc, get_doc, get_limits, list_docs, publish_doc, update_doc. The verbs are clear and the nouns match the resource, though list_docs is a natural pluralization.
With 7 tools, the server is well-scoped for a document publishing platform. Each tool covers a distinct core operation without redundancy or bloat, fitting comfortably in the ideal 3-15 tool range.
The document lifecycle is complete (create, read, update, delete, list), but bundles only have a create operation with no get/update/delete. Also, publish_doc returns a claim_token for anonymous publishes, yet no claim tool is exposed, forcing users to an external endpoint.