Eclipse Beacon MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECLIPSE_BEACON_STATE | No | Override the default state file path. By default, state persists in `data/state.json` beside the server. |
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 |
|---|---|
| policy_ingestA | Ingest a declarations-page-style document (JSON or simple text) from a LOCAL file path. Returns a draft + diff with per-field provenance. DEFAULT IS PROPOSE-ONLY: nothing is written unless confirm=true. Also ingests household_profile JSON (asset/person declarations). |
| policy_listA | List every policy in the household graph with key dates, plus declared assets/persons and current alert windows. |
| policy_getC | One policy in full, including per-field provenance. |
| radar_reportB | Expiry radar: ranked upcoming events (renewal <=60d, premium due <=14d, grace end, escrow proof, enrollment windows [verify]) with severity and consequence. Optional as_of (YYYY-MM-DD) and windows overrides — windows may only be TIGHTENED (longer lead), never loosened (Vigil rule). |
| gap_reportB | Read-only gap analysis: uncovered assets, duplicate coverage, premium spikes vs prior term (default flag >15%). |
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 maps to a clearly distinct operation: write-side ingestion (policy_ingest), read-side retrieval (policy_list / policy_get), and two analytical views (time-based expiry in radar_report vs coverage gaps in gap_report). The two report tools could superficially overlap, but their descriptions explicitly separate temporal alerts from coverage/duplication/premium analysis.
All names are snake_case two-token identifiers, which is easy to read and predict. There is a minor deviation in that policy_* uses a resource prefix with an action second (ingest/list/get), while radar_report and gap_report are noun+report compounds rather than strict verb_noun.
Five tools is well within a focused, well-scoped surface: one write path, two retrieval paths, and two distinct analyses. No tool looks redundant or padded, and nothing appears to be a trivial wrapper.
Ingest plus list/get covers creation and reading, but there is no explicit update, delete, or archive path for policies, assets, or persons (re-ingestion is implied but undocumented as an edit mechanism). There is also no way to acknowledge/snooze alerts or export the household graph, leaving notable lifecycle gaps.