Eclipse Gig Core MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECLIPSE_GIG_CORE_STATE | No | Path to the state file. State persists in `data/state.json` beside the server; override with ECLIPSE_GIG_CORE_STATE. |
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 |
|---|---|
| brief_createB | Create a canonical Task Brief: category, service, scope {statement, items[]}, ZIP-tier location, timing window, ALL-IN ceiling, tip policy, photos (EXIF-strip status recorded per photo), license_required (unknown|no|yes:), safety/access block, intended/prohibited platforms, and a details bag adapters draw native form answers from. Issues the version-1 hash an approval binds to. |
| brief_updateB | Create a new brief version from content-field changes. Any post-approval edit invalidates the approval and returns the brief to draft (approval binds hashes, spec 5.1). |
| brief_approveB | Record the owner's approval of the EXACT current brief hash, plus the per-platform variant hashes approved with it. A hash mismatch is refused. |
| brief_readB | Read a brief with its version, hash, and approval validity. |
| quote_normalizeC | Normalize a quote from any platform model (lead_model, stated_budget, fixed_price, hourly) into one record: face price, itemized fees with bearers, tax, and ALL-IN total kept separate forever. Fees the platform does not expose mark the quote UNEXPOSED with no all-in. Optional ceiling_all_in runs the ceiling test. |
| quote_readB | Read a normalized quote; optional ceiling_all_in re-runs the ceiling test. |
| hire_checkA | Evaluate a hire against a live Procure/Agent Wallet mandate: approved brief hash, mandate presence + expiry, cap vs all-in, brief ceiling, category + platform allowlists, approval threshold (above = owner token for THIS quote), quote expiry, fee exposure. v1 person-selection always needs an owner-confirm token. Returns ALLOW / MANDATE_ALLOW_PERSON_PENDING / DENY with named reasons. Executes nothing; receipted either way. |
| completion_verifyC | Verify completion against the brief's scope statement: each scope item done/partial/not_done with owner attestation. Platform state is stored verbatim and separately; a platform-completed claim the owner does not attest opens an exception record (spec 7.2). |
| review_draftB | Draft review text from a verification record ONLY: what was hired, what was verified, and timeliness/communication/quality strictly as recorded. No sentiment the record does not carry; leverage language is refused at draft time. The draft never submits itself. |
| receipt_listB | List the append-only, hash-chained gig-core receipts and verify the chain. |
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 10 tools
Each tool maps to a clearly distinct action/resource in the gig lifecycle: brief CRUD/approval, quote normalization/read, hire checking, completion verification, review drafting, and receipt listing. There is no meaningful overlap between tools, and descriptions reinforce the boundaries.
All tool names follow a consistent resource_action pattern (brief_read, quote_normalize, hire_check, completion_verify, review_draft, receipt_list). The convention is predictable throughout with no naming-style deviations.
Ten tools is well-scoped for a gig procurement and verification server. Each tool earns its place by covering a distinct stage of the workflow without obvious padding.
The core lifecycle is covered: brief creation/approval, quote normalization, hire checks, completion verification, review drafting, and receipt listing. Minor gaps exist such as no explicit brief_list or quote_list/search operations, but core workflows have no dead ends.