Skip to main content
Glama
heliograph-io

heliograph

Official

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
heliograph_doctorA

Check whether the transport works from here, and change nothing. Run this before a long step: read access is not write access, and finding out afterwards costs a whole round trip through somebody who cannot debug the machine.

heliograph_estatesA

List the configured estates and the transport each uses. Call this first when you do not know which estate to act on.

heliograph_gapsA

Where a run stalled. Returns the intervals in the log's timestamp column, longest first, each attributed to the line BEFORE it, which is what was running. Do this before reading a long log: a hang and slow progress are indistinguishable without it. If every line carries the same timestamp the capture was buffered and the log cannot answer the question at all, which this reports as an error.

heliograph_logsA

List the captured logs, newest first. Each name carries the request id that produced it, so the log for a run you sent is the one whose name matches the id heliograph_send returned. Use this to find a log; use heliograph_read_log to read one.

heliograph_read_logA

Read a captured log whole. Every line carries a UTC timestamp. Read all of it, including the parts that worked: a passing probe beside a failing one is the control that says what the failure means. A green exit means the probes that ran passed, not that the work happened.

heliograph_sendA

Publish a step for the station to run, and return immediately. This does NOT wait for the result: poll heliograph_status until it reports a terminal state, then read the log. The station decides whether to run it at all: a step that declares no mode is refused, and one that changes state needs CONFIRM=yes and a station started with --allow-actions.

heliograph_statusA

What the station is doing now. State is one of starting, running, idle, cancelled, refused, stopped or undelivered. Five of those are terminal: idle, cancelled, refused, stopped and undelivered. starting and running mean the run is still going. An empty state means the station has published nothing yet, which usually means it has not been started. A state you do not recognise is neither finished nor alive: a newer station may publish one, so keep polling rather than giving up. refused is not a failure: it means the station would not run the step, and the reason names the flag that would permit it. undelivered means the run finished and the log is complete but the transport would not take it, so waiting for more is exactly wrong.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct aspect of the heliograph system: estates, transport health, log reading, sending steps, status polling, gap analysis, and log listing. No two tools overlap in function, making misselection unlikely.

Naming Consistency3/5

All tools share the 'heliograph_' prefix, but the suffix varies between bare verbs (send), verb-noun (read_log), and nouns (status, logs, gaps). This mix is readable but lacks a uniform verb_noun pattern, which could reduce predictability.

Tool Count5/5

Seven tools is a well-scoped number for the domain. Each tool serves a clear purpose in the station interaction lifecycle, and there is no bloat or unnecessary duplication.

Completeness4/5

The tool surface covers the core workflows: test transport, send steps, poll status, list and read logs, and analyze stalls. Minor gaps exist (e.g., no tool to start/stop the station or manage configurations), but these appear to be handled externally.

Maintenance

ActivityActive
ResponsivenessResponsive