Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
inspect_placeA

Query the historical and administrative context of a Chinese city, poem landmark, strategic pass, battlefield, or multi-stop route on the Jiangshan Historical Atlas (403 BCE – 2026 CE). Returns the reigning monarch/era, controlling regime (polity), macro-region (dao/lu/province), prefecture (jun/zhou/fu), modern province/city, 2,400-year city/pass lore, and a shareable deep-link URL.

inspect_personA

Query the spatio-temporal life & poetry chronicle (点人溯事) of a single Chinese historical figure/monarch, or compare 2–4 figures for shared encounters & parallel lives (同途相逢 / 时空平行对照) on the Jiangshan Historical Atlas. Returns biographical summary, chronological geocoded stops, shared encounter events, and a shareable deep-link URL.

search_atlasC

Search the Jiangshan Historical Atlas across 1,753 ancient cities, 185 poetic/battlefield landmarks, 20 strategic mountain passes, 113+ historical figures, 351 imperial eras, and 471 chronological milestones.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct roles: inspect_place retrieves place context, inspect_person retrieves person/compare context, and search_atlas performs cross-entity discovery. While search can surface cities or figures also handled by the inspect tools, the search-vs-inspect boundary is explicit and easy for an agent to apply.

Naming Consistency5/5

All names follow a consistent verb_noun pattern: inspect_place, inspect_person, search_atlas. The convention is predictable and readable, with no mixing of camelCase, vague verbs, or inconsistent action styles.

Tool Count4/5

Three tools is minimal but reasonable for a focused read-only historical atlas: one discovery tool and two entity-specific inspectors. It sits at the low end of the appropriate range, so it is slightly thin but not mismatched to the purpose.

Completeness4/5

The surface covers the core read-only workflows: search across the atlas, inspect a place or route, and inspect/compare people. Minor gaps remain, such as no dedicated timeline/era browse or explicit list operation, but search_atlas mitigates these enough that agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessResponsive