Cyan Eclipse Routeseal
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECLIPSE_ROUTESEAL_STATE | Yes | Record store path. | |
| ECLIPSE_ROUTESEAL_POLICIES | Yes | Operator's stated routing policies, as JSON. | |
| ECLIPSE_ROUTESEAL_ADAPTER_KEYS | Yes | Dispatch-point adapter keys, as JSON. Operator-held in production; the keys in `keys/` are test fixtures only. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| routeseal_seal_dispatchA | Seal a routing decision at a buyer-controlled dispatch point, through the dispatch-point adapter channel with the adapter's attestation, and mint the verdict under the operator's stated routing policy. One metered op per dispatch seal; decision-only and below-standard captures do not meter. Routeseal seals the routing decision at the moment of dispatch — the task, the candidates the router passed over, the target it chose, and the reason it stated. If the choice diverged from your stated routing policy, or picked an affiliated target over the policy's preferred candidate, the sealed record says so, and anyone can recompute the verdict from the record itself. |
| routeseal_get_verdictB | The full verdict record for a dispatch seal: verdict, named clause, selected target, policy-preferred candidate passed over, grammar and policy versions, receipt refs. Unmetered. |
| routeseal_checkC | Counterparty view: the verdict class and the named clause only. Unmetered. |
| routeseal_recomputeA | Recompute a verdict from an exported capture plus the grammar and policy versions, with no service state. Unmetered. |
| routeseal_export_capturesB | Export a sealed capture with the receipt chain head and the grammar and policy versions, for independent recomputation. Unmetered. |
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 5 tools
Each tool has a distinct role in the seal/export/verify pipeline, but get_verdict and check both return verdict information and could be momentarily confused despite the 'full record' vs 'counterparty view' distinction. export_captures and recompute are clearly separated as producer and consumer of captures.
All tools share the routeseal_ prefix, but the verb pattern is mixed: three use verb_noun (export_captures, seal_dispatch, get_verdict) while check and recompute are bare verbs. Mostly readable and predictable, with minor deviation.
Five tools is well-scoped for a narrow sealed-routing-verdict service: one write path, two read paths, plus export and recompute utilities. Each tool earns its place without redundancy.
The core lifecycle — seal a dispatch, export a capture, recompute independently, retrieve full and counterparty verdicts — is fully covered. Minor gaps exist around discovering/listing existing seals and policy registration or updating, which agents may need to work around.