Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
INARA_API_KEYNoAPI key for Inara (optional, but required for Inara tools)
ED_JOURNAL_DIRNoDirectory containing Elite Dangerous journal files (optional, overrides default locations)

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_commander_statusC

Commander name, current system/station, ship, credits from local journals.

get_current_locationB

Current system + coords + station from latest Location/FSDJump/Docked event.

get_ship_loadoutB

Current ship + modules from latest Loadout event.

get_journal_historyC

Recent relevant journal events, newest first (FSDJump, Docked, Loadout, ...).

get_ship_purchase_historyB

Your actual ship purchase history from journal events (ShipyardBuy/ShipyardSell).

Returns real purchase prices, stations, systems, timestamps — useful for comparing current market prices vs what you actually paid, spotting discounts.

get_module_purchase_historyB

Your module purchase history from journal events (ModuleBuy/ModuleSell/ModuleRetrieve).

Returns real purchase prices, stations, systems, timestamps — useful for comparing current outfitting prices vs what you actually paid.

edsm_sphere_systemsC

Systems within radius_ly of a system name or x/y/z coords (EDSM).

edsm_system_infoC

Population/government/stations for one system + claimable assessment (EDSM).

spansh_find_nearby_stationsC

Stations nearest to galactic coords, slimmed for shopping lists (Spansh).

spansh_query_systemsC

Flexible Spansh systems search, e.g. {"population": {"value": [0,0]}}.

inara_search_nearestC

Nearest stations/systems via Inara API (needs INARA_API_KEY + app access).

Falls back to website search URLs when the API app has no access.

inara_website_searchC

Inara website search links + page check (no API key needed).

eddn_live_sampleB

Bounded sample of live EDDN relay messages (needs pyzmq + network).

schema: substring filter on $schemaRef, e.g. "commodity". None = all.

find_colonisation_candidatesB

Zero-pop, claimable systems near a constellation/centre.

centre: 'teapot' (Sagittarius asterism) or an EDSM system name or 'x,y,z'. Workflow: resolve Teapot anchor stars -> EDSM sphere search per anchor -> batch detail lookup -> filter zero-pop/uncontrolled/stationless -> dedupe.

build_cargo_shopping_listC

Anaconda max-cargo module list + where to buy near your current location.

Uses journals for current system/coords + owned modules, Spansh for nearby stations with outfitting, EDSM sphere as fallback. Prices/stock rotate; verify at the station.

find_exobiology_targetsB

Best exobiology targets near you: organic-rich systems with estimated turn-in.

Uses Spansh bodies search for organic-life bodies, ranks systems by estimated turn-in credits (body value x biology multiplier). Returns per-system body breakdown with distance and estimated value.

get_exobiology_samplesB

Exobiology sample status: discovery, FSS progress, estimated turn-in credits.

Reads local journals for FSSAllBodiesFound / ScanOrganic / SAAScanComplete events. When FSS complete, uses EDSM estimated system value for turn-in credits. community_discovered=True means FSS complete OR EDSM has catalogued bodies (others discovered before you).

get_cargo_holdC

Current cargo manifest + rack capacity + free space (Cargo.json + Loadout).

get_station_marketB

Live market at your docked station (Market.json): prices/supply/demand.

get_station_outfittingC

Outfitting stock at your station (Outfitting.json + ModulesInfo.json).

get_station_shipyardC

Shipyard stock at your station (Shipyard.json).

get_fleet_overviewB

Every ship in your journals + computed cargo per ship (latest first).

get_wallet_summaryC

Credits now + lifetime MarketBuy/MarketSell/MissionCompleted sums.

get_odyssey_stateC

On-foot state: Backpack + ShipLocker + latest suit loadout events.

find_stored_shipA

Locate a stored ship: station/system + transfer cost/time.

Matches name or ship type (case-insensitive); omit query to list all. Latest StoredShips sighting per ship wins.

spansh_search_stationsC

Full Spansh /stations/search passthrough (pads/services/market filters).

find_commodityB

Best stations trading a commodity near you (live Spansh market snapshots).

mode 'buy' = station has supply; 'sell' = station has demand. Sorted by stock size then distance. Stock rotates; verify in-game before flying.

find_multi_supplyA

One station covering a whole shopping list (live Spansh markets).

commodities maps name -> minimum supply for one full load, e.g. {"Steel": 2000, "Titanium": 2000}. Scans pages x 100 nearest stations (default 4, max 10); full-cover stations first, then most lines covered, then nearest. Stock rotates; verify in-game before flying.

find_moduleB

Stations selling a module near you (matches name or ed_symbol, live Spansh).

Scans pages x 100 nearest stations (default 1, max 10): Spansh outfitting snapshots are sparse, so one page misses stock. Each hit carries acquisition ("credits" vs "special") — pre-engineered/tech-broker/ Powerplay stock (e.g. mercgear) is NOT a plain credit purchase. standard_only=True drops special-acquisition hits.

find_shipB

Stations selling a ship near you (live Spansh shipyard lists).

Scans pages x 100 nearest stations (default 4, max 10): Spansh shipyard snapshots are sparse, so one page misses stock. Each hit carries a price_note reminding you to verify the price in-game — ship discounts are time-limited and not exposed in Spansh public snapshots.

station_servicesA

Services/pads/market for a named station (live Spansh).

Duplicate station names exist across systems: pass system_name (full name) to disambiguate, otherwise all matches are returned. Flags the System Colonisation contact explicitly. Stock snapshots rotate; verify in-game before flying.

get_colony_progressA

Colony build scoreboard from your journals (latest depot manifest).

Per-commodity required/provided/remaining plus totals, overall progress, claimed system, your-vs-others tonnage, delivery pace and ETA vs the 28-day window. Returns found False when no claim/beacon exists yet.

get_stored_modulesA

Modules you own in storage, per station (StoredModules journal events).

Check here before buying: a stored module only needs a transfer. Open outfitting/storage in-game to refresh a station's entry.

spansh_search_bodiesC

Exploration search over Spansh bodies (e.g. Earth-likes near a reference).

system_distanceB

Light-year distance between two systems (live EDSM coords) + jump estimate.

find_local_opportunitiesA

What's profitable near you: trade hubs, mission ports, exobio frontier.

Live EDSM sphere around a system (or your journal location) grouped into money-making buckets. Buckets only — follow up with find_commodity or station_services before flying.

get_exploration_logB

Per-system survey ledger from YOUR journals (COMPLETE/PARTIAL/VISITED).

grade: optionally filter to one grade. limit caps rows (default 50).

system_scan_statusB

How deeply has ONE system been scanned — community catalog + your log.

Community: live EDSM bodies catalog count + type break-down + scan value. You: matching journal row (visits/FSS/scans/mapped) if ever visited.

find_search_backlogB

Systems near a reference YOU have not fully scanned (Raxxla grid backlog).

Cross-references live EDSM sphere (with bodyCount) against your journal ledger: UNVISITED first, then VISITED-but-incomplete. Confirm in-game.

create_experimentB

Define a bounded scientific experiment with provenance tracking.

Creates an experiment definition that can be tracked with runs, results, and controls. Parameters and control design should be minimal and deterministic.

run_experimentB

Create a new run of a bounded scientific experiment.

Records the run start time, software version, model/provider metadata if applicable, and optional random seed. The agent should invoke approved MCP tools to populate results, then call complete_experiment.

complete_experimentB

Mark an experiment run as complete with results or error.

Records completion time, result summary, and any error message. The agent should have gathered results from approved MCP tools before calling this.

save_observationC

Save a provenance-tracked source observation to the research store.

All missing data is explicitly marked rather than silently converted. Returns the observation ID and provenance summary.

get_experiment_resultB

Retrieve a completed experiment run's results with full provenance.

Returns the stored run with result summary, provenance observations, and metadata.

list_experiment_runsB

List all runs for an experiment (or all experiments).

Returns run summaries ordered by start time descending.

list_observationsB

List provenance-tracked observations with filtering.

Filters by source and/or system name. Never silently converts missing values; all observations retain their missing/observed status.

query_bounded_regionB

Query a bounded EDSM sphere region with full provenance tracking.

Caps results at 200 systems to keep responses bounded. Systems missing coordinates are explicitly marked rather than silently dropped. Returns region metadata, system list with provenance, and any errors.

build_system_graphB

Build a jump-range proximity graph for a bounded EDSM sphere.

Queries EDSM for systems within radius_ly, then constructs edges between all pairs within max_edge_distance. Returns graph snapshot with nodes, edges, and metadata. Missing coordinates are preserved as isolated nodes with explicit missing flags.

analyze_graph_metricsC

Build a graph and compute structural metrics in one call.

Returns: connected components, degree distribution, bridges, articulation points, betweenness centrality, and motif counts.

graph_sensitivity_analysisC

Run graph construction across multiple jump-range radii.

Returns per-radius metrics for parameter sensitivity testing.

find_spatial_clustersB

Find DBSCAN spatial clusters in a bounded EDSM sphere.

Queries EDSM for systems within radius_ly, extracts coordinates, then runs DBSCAN with eps_ly and min_samples. Returns clusters, noise points, and per-point assignments. Systems without coordinates are excluded from clustering but noted.

analyze_spatial_geometryC

Analyze geometric structure of systems in a bounded EDSM sphere.

Computes linearity, planarity, spread, centroid, compactness, and nearest-neighbor statistics to identify linear arrangements, planar structures, or spherical clusters.

spatial_sensitivity_analysisB

Run DBSCAN across parameter combinations for sensitivity testing.

Returns per-parameter-set cluster counts, noise counts, and cluster details to assess robustness of spatial patterns.

aggregate_temporal_eventsB

Aggregate timestamped EDDN/journal events into a time series.

Returns intervals with event-type counts. Systems without timestamps are skipped (not silently converted to zero).

detect_temporal_outliersC

Robust outlier detection on event counts for a given interval.

Methods: 'IQR' (interquartile range) or 'zscore' (standard deviations). Returns per-event-type outlier flags and statistics.

detect_change_pointsB

Detect change points using sliding window mean comparison.

Compares early vs late window means; flags changes exceeding sensitivity * MAD. Works on per-event-type time series.

normalize_temporal_activityB

Normalize activity counts by accessibility/traffic indicators.

Methods: 'traffic_normalized', 'population_normalized', 'raw'. Returns normalized series with caveats for missing data.

check_temporal_persistenceC

Check persistence of anomalous patterns across two time windows.

Returns per-event-type persistence flags with relative proportion change.

Prompts

Interactive templates invoked by user choice

NameDescription
colonisation_survey
anaconda_cargo_refit
trade_run
raxxla_survey

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 58 tools

Disambiguation3/5

The 58 tools span many distinct domains, but several station-search and analytics tools overlap in purpose, e.g. find_ship/find_module/find_commodity vs spansh_search_stations/station_services, and analyze_graph_metrics vs graph_sensitivity_analysis. Descriptions help distinguish them, but the sheer number and similar patterns create real misselection risk.

Naming Consistency3/5

All names use snake_case and are readable, but the convention is mixed: verb-first names (get_, find_, build_, analyze_, create_, list_) coexist with source-prefixed names (spansh_, edsm_, inara_, eddn_) and noun-only names such as system_distance and station_services. There is no single predictable pattern throughout.

Tool Count1/5

At 58 tools, the server is far beyond a well-scoped 3–15 tool set and exceeds the 25+ threshold where sprawl becomes a usability problem. Many tools are specialized analytics or data-source variants, making the surface feel like multiple MCP servers combined into one.

Completeness4/5

Coverage is broad across journal state, trade/outfitting, exploration, exobiology, colonisation, and research analytics. There are still notable gaps for a full Elite Dangerous assistant, such as missions, engineering/blueprints, combat, powerplay, and deleting/updating research records, but core data workflows are well represented.

Maintenance

ActivityMaintained
ResponsivenessOutdated data