Magic Lane MCP Docs Server

Official

by magiclane

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List recently updated Magic Lane documentation

list_recent_updates

Read-onlyIdempotent

Report documentation pages updated within a chosen window and source, so you can track SDK documentation changes without re-reading everything.

Instructions

Report which documentation pages were updated within the last N days, per source, using each page's embedded 'Last updated' date. Useful for tracking SDK documentation changes without re-reading everything. Covers every source, including the developer guides. When nothing falls in the window, the response names the newest date there is and lists the newest pages.

Input Schema

Name	Required	Description	Default
`days`	No	Look-back window in calendar days (UTC), inclusive: 1 = yesterday and today.
`limit`	No	Maximum number of pages to report.
`offset`	No	How many of the window's pages, newest first, to skip: the nextOffset of the previous answer.
`source`	No	Restrict to one documentation source.	all

Output Schema

Name	Required	Description
`days`	Yes
`total`	Yes	Pages dated within the window (updates holds `limit` of them from `offset`).
`offset`	Yes
`source`	Yes
`message`	Yes	A one-line summary of the result.
`updates`	Yes	Pages dated within the window, newest first.
`newestDate`	No	The newest "Last updated" date among the selected sources' pages (absent when none carries one).
`nextOffset`	No	The offset that lists the next pages; absent at the end.
`newestPages`	Yes	Only when updates is empty: the newest pages the selected sources have, all older than the window.
`failedSources`	Yes	Source files that could not be loaded: "index" (llms.txt) or "full-text" (llms-full.txt) — a problem with the files on developer.magiclane.com or with reaching it, never a gap in the documentation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds genuinely new behavior: the recency signal comes from each page's embedded 'Last updated' date, and the empty-window case degrades gracefully by naming the newest date and listing newest pages. That fallback behavior is exactly the kind of context annotations cannot carry.

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?

Front-loads the core action and scoping, then the use case, then the empty-result behavior. Four sentences with little waste, though 'Covers every source, including the developer guides' is marginally redundant with the source parameter.

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?

An output schema exists and covers return shape, and the description usefully documents the no-results fallback. The one gap is that pagination (limit/offset and the nextOffset chaining) is never mentioned in the description, which matters for an agent iterating over a window, though the schema does document it.

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%, so all four parameters (days, limit, offset, source) are fully self-documented, establishing a baseline of 3. The description reinforces 'last N days' and 'per source' but adds no syntax, format, or interaction detail beyond the schema.

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 and resource ('report which documentation pages were updated') plus scope ('within the last N days, per source') and the underlying data source ('embedded Last updated date'). The phrase 'tracking SDK documentation changes without re-reading everything' implicitly separates it from read_doc/read_docs_batch, so an agent can route 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 context ('tracking SDK documentation changes without re-reading everything') and states the coverage scope ('every source, including the developer guides'). It does not explicitly name alternatives like search_docs or list_docs or state when NOT to use it, so it falls short of a 5.

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

Deploy Server