Find a topic across all Magic Lane SDKs
find_across_sdksFinds matching documentation for one topic across every Maps SDK and Cloud REST API side by side, enabling cross-platform comparisons.
Instructions
Given one topic (e.g. "add markers", "calculate route", "offline maps"), return the best-matching documentation page(s) for EVERY source side by side — developer guides, the Maps SDKs for Flutter, Android, iOS, C++, TypeScript, and the Cloud REST APIs. Ideal for cross-platform comparisons ("how do I do X on iOS vs Android"; platform names in the query are ignored unless they are part of a feature name, such as "Android Auto", or of a page's title, such as "integrate the sdk", or name the product itself, such as "REST API" — a query that is the title of one of the Cloud REST APIs, such as "geofences api", is answered by that API alone; a query about the platforms themselves, such as "flutter vs android", is answered by each named platform's own overview page). A source reports "(no match)" unless a page matches at least half of the topic words (half in its own title or description, not only in its section) and is about the most specific one: it is in the page's title or section, or in its description or path with every other word too (every word when even that one is common, such as "map"). A topic of one or two words must match in full, and a single one must head the page — unless the title holds the query's other word ("Update Content" for "update maps"), or no page is headed with the word the page lacks there — no page of its source for a word its index entry lacks, no page at all for a single word (never a word next to "API"): then a page whose own text (llms-full.txt) names the missing word at least twice answers, marked as covering part of the topic ("landmark store"; the Cloud's Territory for "generate territories"), and a page whose description names the single word as written (not "key" for "token") in its first sentence and its first two thirds answers when its text names it again ("waypoints"); a page may always lack an action word ("upgrade to 3.1.4") or the words of setting up ("set up navigation"). A word the page has only in its section does not count when its own title and description hold less than half of the query's words ("handle route events" is not "Social Event Voting", filed under Routing & Navigation). A page that only mentions the topic in passing is not listed; search_docs finds those.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The topic to look up in every SDK, e.g. "add markers". | |
| limitPerSource | No | How many matches to return per source. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| topic | Yes | The query without platform and comparison words — what was looked up. | |
| message | Yes | A one-line summary of the result. | |
| sources | Yes | Every documentation source, in a fixed order. | |
| unverified | Yes | Platform words left out of the topic that could not be checked against their platform's page titles (the index of `source` did not load), so one may be part of a feature name ("Android Auto") instead. | |
| 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. |