Cyan Eclipse Grantseal
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECLIPSE_GRANTSEAL_STATE | No | Record store path. | |
| ECLIPSE_GRANTSEAL_RUNTIME_KEYS | No | Principal-side runtime channel keys, as JSON — principal-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 |
|---|---|
| grantseal_seal_grantB | Seal the exact scope granted at connect time, as presented by the principal-side connect flow: granted scope set, connector identity, agent identity, and the integration class (F = grant seal + runtime use capture; G = grant seal only). One metered op per grant seal. Grantseal seals the exact permissions an agent or app was granted at connect time, and the permissions it actually exercised as captured in your own agent runtime. If it used a scope it was never granted — or a renewal quietly added scopes — the sealed record names them, and anyone can recompute the verdict from the record itself. |
| grantseal_capture_useB | Present an exercised-scope capture from the principal's own agent runtime (Class F records only) and mint the diff verdict against the original sealed grant. Captures from any other provenance are rejected. One metered op per use-window diff; UNVERIFIABLE captures do not meter. |
| grantseal_seal_renewalA | Seal a renewal or re-connect grant and diff it against the original seal at presentation: added scopes verdict EXPANDED-AT-RENEWAL naming them; a renewal that changes nothing records a no-change marker. Renewals do not meter. |
| grantseal_get_verdictC | The full verdict record for a grant seal: verdict, use verdict facet, named out-of-scope and added scopes, taxonomy version, receipt refs. Class G records return GRANT-SEALED. Unmetered. |
| grantseal_checkC | Counterparty view: the verdict class and the names of out-of-scope or added scopes only. Unmetered. |
| grantseal_recomputeB | Recompute a verdict from the exported captures plus the taxonomy version, with no service state. Unmetered. |
| grantseal_export_capturesB | Export the sealed captures for a grant (grant capture, latest use capture, renewal records) with the receipt chain head and taxonomy version, 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 7 tools
The core lifecycle tools (seal_grant, seal_renewal, capture_use, export_captures) each target a clearly distinct operation. However, get_verdict, check, and recompute all return verdict-like data, distinguished only by scope of disclosure and statefulness; an agent could plausibly misselect between get_verdict and check when it just wants 'the verdict'.
All tools share a uniform grantseal_ prefix followed by a verb_noun pattern (seal_grant, capture_use, export_captures), which is highly predictable. The two bare-verb exceptions, grantseal_check and grantseal_recompute, are minor deviations that remain readable.
Seven tools is well within the ideal range and each maps to a distinct step in the seal/capture/verdict/recompute workflow. No tool appears redundant filler, and the surface is neither thin nor bloated.
The surface covers the full lifecycle: seal initial grant, capture exercised use, seal renewal, retrieve verdict, counterparty check, stateless recompute, and export for independent verification. The main gap is discovery/listing — there is no way to enumerate seals by agent or connector identity, so callers must already hold an identifier.