alphaledger
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.
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fingerprintA | Identify a factor WITHOUT consuming a trial. Returns the value fingerprint, whether the ledger has seen it, and its position if so. Call this before writing new factor code to avoid re-testing something already counted. |
| evaluateB | Measure one factor and record it as a trial. Returns cross-sectional RankIC, Newey-West t, single-test p, the trial's index within its family, and the family-adjusted verdict. This is the only supported way to produce evidence. |
| gateA | Re-judge an already-recorded trial against its family, optionally at a different alpha. Use after importing more trials or to ask 'how much better would this need to be'. |
| ledger_statsB | How much has been tried, and where the session is going in circles: repeated evaluations, sign flips, near-duplicate clusters, and the cross-family error rate. |
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 4 tools
Each tool has a distinct role: fingerprint checks identity without a trial, evaluate records evidence, ledger_stats summarizes behavior, and gate re-judges existing trials. The only mild overlap is between evaluate and gate, both of which return family-adjusted verdicts, but their preconditions and use cases are clearly separated.
All names are lowercase snake_case and readable, but they mix noun-style names (fingerprint, gate, ledger_stats) with a verb (evaluate). There is no single predictable verb_noun or noun pattern throughout.
Four tools is well-scoped for a focused factor-research ledger. Each tool covers a distinct part of the workflow and none feels redundant or excessive.
The core lifecycle is covered: identify a factor, evaluate and record it, inspect ledger health, and re-judge recorded trials. Minor gaps exist around listing or retrieving individual trials and explicit import/export operations, though these may be intentionally outside the server's scope.