Ortho Earth
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Ortho Earth is an open-source 3D globe map engine for the browser (WebGPU with a WebGL2 fallback, no API key). Use get_facts before quoting a version or a compatibility number, get_started for the tested setup recipe, check_compat to see whether a MapLibre GL JS or CesiumJS feature works, lookup_api for exact signatures, search_docs for anything else, and view_link to show a place on the globe.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_factsA | Latest version and release date, npm packages, licenses, and how many official MapLibre GL JS and CesiumJS examples run unchanged on Ortho Earth. Rebuilt on every deploy of www.ortho-earth.com. Call this before stating a version number or a compatibility figure. |
| search_docsA | Full-text search over the Ortho Earth documentation (the recipe, the changelog, migration guides from MapLibre GL JS, CesiumJS, Leaflet and Google Maps, the engine overview, GeoPBF, Gint, comparison articles). Returns the best matching sections with their source page. |
| get_startedA | The step-by-step recipe for putting the Ortho Earth globe in a web page, with the exact file contents. Every step is run by an automated test against the published npm packages. route "vite" = npm + Vite project with @ortho-earth/globe (recommended); route "html" = a plain HTML page without a bundler. |
| check_compatA | Looks up how the official MapLibre GL JS examples and CesiumJS Sandcastle examples matching the query run on Ortho Earth (same picture / same answers / runs partly / does not run), with notes and links to side-by-side comparisons, and how MapLibre style properties are read (e.g. "fill-extrusion", "line-dasharray"). |
| lookup_apiA | Returns the TypeScript declaration (with its doc comment) of an Ortho Earth API from the published types: createGlobe and its options (globe.d.ts), the map object it returns (globe-map.ts), and the MapLibre-compatible facade (maplibre.d.ts). Doc comments are partly in Japanese. |
| view_linkA | Makes a www.ortho-earth.com link that opens the 3D globe at a place, and the matching view string for createGlobe({ view }). zoom uses the same scale as the view string (about 0–2 for the whole Earth, 12 for a city). app "japan" adds Japan's detailed basemap and PLATEAU 3D buildings. |
| list_appsA | The apps and demos on www.ortho-earth.com, each with its link and a one-line description. Useful for showing what the engine can do. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource: version facts, prose docs search, setup recipe, example-compatibility lookup, TypeScript declarations, share-link generation, and demo listing. The only soft overlaps are between search_docs (which indexes comparison/changelog content) and check_compat, and between get_facts and the changelog inside search_docs, but the descriptions draw workable boundaries.
All names are snake_case verb_noun pairs (get_facts, search_docs, check_compat, lookup_api, list_apps, view_link), which is predictable. The minor deviation is the use of several near-synonym retrieval verbs (get/search/check/lookup/view) rather than one, though the verb choice loosely signals the resource type.
Seven tools is tight and well-scoped for a documentation/API companion server; each tool covers a clearly different need. Nothing feels padded or missing at the count level.
The surface covers the read-only lifecycle an agent needs: facts, doc search, setup, compatibility, API signatures, links, and demos. Minor gaps remain, notably no way to enumerate available API symbol names (lookup_api appears to require knowing the name) and no dedicated migration/troubleshooting entry point beyond generic doc search.