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.

Evidence-first geolocation. Call explain_rules once, then fleet_status for the whole picture. Report each confidence state verbatim; never present an INDICATED claim as settled. When a lane is OPEN and the origin is behind a CDN, cite a provider page with record_fact rather than guessing.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
resources
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
locate_modelA

Resolve where a model's inference physically runs. Accepts a model id, a fleet lane/CLI name, or an explicit base_url. Returns a four-plane location card (control/edge/origin/legal), the serving chain, evidence rows with sources, a confidence state, contradictions, and the next probe that would tighten the answer. Re-derives everything from live DNS, ASN, cloud prefix tables and PeeringDB, so it tracks provider changes without redeploying.

fleet_statusA

Run locate_model across every catalog provider that has a known API host and return one summary table: publisher, serving entity, edge operator, country/region, precision and confidence per lane. The one call to re-run whenever the fleet or a provider changes.

trace_endpointA

Resolve one hostname into a serving chain: CNAME hops, addresses, ASN and org, registry RDAP, and the published cloud region of each address. Flags CDN/anycast addresses so an edge PoP is never mistaken for an origin.

lookup_prefixB

Identify a single address: ASN and org, the cloud's own published region for the prefix, RDAP registration, and PeeringDB facilities. The published cloud region outranks any geoIP database.

find_regional_endpointsA

Search certificate transparency logs for subdomains of a domain and surface ones that look regional (-eu, -jp, -sg, -cn ...). Providers often run regional endpoints that no documentation mentions.

probe_latencyB

Measure a host from distributed vantage points and test the physical RTT floor. Returns per-probe implied maximum distance, an anycast verdict, and a FALSIFIED verdict when a measurement is impossible for the claimed origin.

inspect_edgeA

Read response headers from an ENTITLED endpoint only (config.json allowlist) and report the TLS-terminating PoP. Explicitly an edge-plane fact: it never establishes where inference ran.

record_factA

Add a provider residency or facility fact to the catalog, citing a source URL and a verbatim quote. This is how the catalog learns: a verified fact becomes a tier-A anchor and lifts the matching card to ANCHORED. Pass publisher + match[] to add a provider that is not in the catalog yet.

observe_endpointsA

Run a lane's one-line probe prompt (fleet.json observe.argv) and record every outbound connection: a logging CONNECT proxy (every OS), the OS socket table for the process tree (ss / lsof / netstat), and on Linux strace for TLS SNI and DNS names. Nothing is decrypted. Settles the CONTROL plane only - observed hosts end at the TLS edge, never the inference origin. Spends one model call per lane, so it only runs with run:true; without it, it returns the commands it would run.

explain_rulesA

Return the source precedence, plane definitions, confidence states and the RTT falsifier used by every other tool.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
geolocation rulesPrecedence, planes, confidence states, RTT falsifier.
provider catalogThe only hand-maintained data, with verification dates.

TDQS

A3.8/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target clearly different objects: locate_model (model→location card), trace_endpoint (hostname→serving chain), lookup_prefix (IP→ASN/region), fleet_status (batch roll-up). The closest pairs are trace_endpoint vs lookup_prefix (hostname vs address, both emitting ASN/RDAP/cloud region) and inspect_edge vs observe_endpoints (both probes, different planes), but the descriptions explicitly disambiguate by input type and plane.

Naming Consistency4/5

All names are snake_case and almost all follow verb_noun (inspect_edge, record_fact, probe_latency, locate_model, trace_endpoint, lookup_prefix, explain_rules). The one deviation is fleet_status, a noun-only name, which breaks the pattern slightly but remains readable in context.

Tool Count5/5

Ten tools is well within the sweet spot and each maps to a distinct investigation step (edge, control, origin, legal, catalog write, discovery, falsification, meta). No tool feels redundant filler, and none of the planes is served by more than one or two tools.

Completeness4/5

Coverage is strong across the four planes: inspect_edge (edge), observe_endpoints (control), trace_endpoint/lookup_prefix/locate_model (origin), record_fact (catalog write), plus fleet_status and explain_rules. The notable gap is the catalog read/delete side — record_fact writes facts but there is no tool to list, inspect, or retract a fact, so bad entries cannot be corrected without re-recording.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues