England Works Watch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EWW_X402_PAY_TO | No | The payment recipient address for x402. Required when EWW_PAYMENT_ENFORCED is enabled. | |
| EWW_PAYMENT_ENFORCED | No | Controls whether payment is enforced. When enabled, EWW_X402_PAY_TO is mandatory. Accepts 'true' or 'false'. | false |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sponsor_change_checker_infoA | Explain the UK Skilled Worker sponsor-change checker scope and supported decision states. |
| list_supported_change_eventsA | List sponsor-change event types this checker can assess for Skilled Worker sponsor duties. |
| licensing_source_statusA | Check freshness and review status of the official GOV.UK evidence used by the sponsor-change checker. |
| assess_change_impactA | Check whether a specific employee/company change affects UK Skilled Worker sponsor duties. Use for salary, role, work-location, absence, delayed-start, stop-sponsoring, organisation, TUPE, merger or takeover changes. Use only facts explicitly supplied by the user; never infer or default missing compliance facts such as same_salary_option_still_met. Pass omissions through so the deterministic engine can return INSUFFICIENT_INPUT. Returns an evidence-linked decision and required next action. |
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 purpose: explaining scope, listing event types, checking source freshness, and assessing impact. There is slight overlap between the info and event-list tools, but the descriptions clarify their different roles.
Two tools use a verb-led pattern (list_supported_change_events, assess_change_impact), while the other two are noun phrases (sponsor_change_checker_info, licensing_source_status). The naming is readable and consistent in style, but not fully uniform.
Four tools are well-scoped for this narrow domain: one for context, one for supported events, one for evidence freshness, and one for the core assessment. Each tool earns its place without redundancy.
The server covers the main checker workflow: understanding scope, enumerating supported changes, verifying source freshness, and assessing impact. Minor gaps like returning raw evidence details or a dedicated decision-state lookup are workable around.