RegEvidenceHub Sponsor

assess_change_impact

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payload`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 20, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / payload / description

Removed value: -"One structured Skilled Worker sponsor-change event. Supply the event-specific facts you know; missing required decision facts fail closed rather than being guessed."

removedInput schema / properties / payload / examples

Removed value: -[
-  {
-    "consecutive_working_days": 11,
-    "event_type": "unauthorised_absence",
-    "route": "skilled_worker"
-  }
-]

removedInput schema / properties / payload / properties

Removed value: -{
-  "change_kind": {
-    "description": "For organisation_change or TUPE: the specific organisation or transfer change being assessed.",
-    "type": "string"
-  },
-  "change_type": {
-    "description": "For merger_takeover: merger, takeover, or similar sponsor-organisation change type.",
-    "type": "string"
-  },
-  "compelling_reason": {
-    "description": "For an absence: whether a compelling reason is established under the sponsor-duty rule.",
-    "type": "boolean"
-  },
-  "consecutive_working_days": {
-    "description": "For unauthorised_absence: consecutive working days absent without authorisation.",
-    "minimum": 0,
-    "type": "integer"
-  },
-  "delay_days": {
-    "description": "For worker_start_delay: days after the relevant Skilled Worker start-date trigger.",
-    "minimum": 0,
-    "type": "integer"
-  },
-  "direction": {
-    "description": "Whether the salary change increases or decreases pay.",
-    "enum": [
-      "increase",
-      "decrease"
-    ],
-    "type": "string"
-  },
-  "duties_unchanged": {
-    "description": "For TUPE or merger/takeover: whether the worker's duties remain unchanged.",
-    "type": "boolean"
-  },
-  "event_type": {
-    "description": "Sponsor change event category to assess: absence; salary; role or occupation-code change; work-location or home-working change; delayed start; stopping sponsorship or worker departure; organisation change; TUPE transfer; or merger/takeover.",
-    "enum": [
-      "worker_start_delay",
-      "unauthorised_absence",
-      "unpaid_or_reduced_pay_absence",
-      "salary_change",
-      "role_change",
-      "work_location_change",
-      "stop_sponsoring",
-      "organisation_change",
-      "tupe_transfer",
-      "merger_takeover"
-    ],
-    "type": "string"
-  },
-  "hybrid_only": {
-    "description": "For work_location_change: whether work remains hybrid with the main office unchanged.",
-    "type": "boolean"
-  },
-  "new_client_site": {
-    "description": "For work_location_change: whether the worker has a new normal client site.",
-    "type": "boolean"
-  },
-  "new_entity_has_relevant_licence": {
-    "description": "For merger_takeover: whether the new entity has the relevant sponsor licence.",
-    "type": "boolean"
-  },
-  "new_main_office": {
-    "description": "For work_location_change: whether the worker has a new normal main office or branch.",
-    "type": "boolean"
-  },
-  "new_sponsor_has_relevant_licence": {
-    "description": "For TUPE or merger/takeover: whether the receiving sponsor holds the relevant sponsor licence.",
-    "type": "boolean"
-  },
-  "occasional_only": {
-    "description": "For work_location_change: whether the location change is only occasional and day-to-day.",
-    "type": "boolean"
-  },
-  "old_entity_continues_trading": {
-    "description": "For merger_takeover: whether the old sponsor entity continues trading after the change.",
-    "type": "boolean"
-  },
-  "permanent_remote": {
-    "description": "For work_location_change: whether the worker moves to permanent or full-time home working.",
-    "type": "boolean"
-  },
-  "pre_registration_nurse_or_midwife": {
-    "description": "For salary_change: whether the worker is a pre-registration nurse or midwife covered by the modeled salary branch.",
-    "type": "boolean"
-  },
-  "reason": {
-    "description": "Reason for stopping sponsorship or the worker's departure, or the relevant organisation-change reason.",
-    "type": "string"
-  },
-  "revised_salary_meets_skilled_worker": {
-    "description": "For salary_change: whether the revised salary still meets a Skilled Worker salary basis.",
-    "type": "boolean"
-  },
-  "role_eligible": {
-    "description": "For role_change: whether the proposed role is eligible under the Skilled Worker route.",
-    "type": "boolean"
-  },
-  "route": {
-    "description": "Visa route for the sponsor-duty decision. V0.1 supports Skilled Worker only; unsupported routes fail closed.",
-    "enum": [
-      "skilled_worker"
-    ],
-    "type": "string"
-  },
-  "salary_requirements_met": {
-    "description": "For role_change: whether the proposed role and pay continue to meet applicable salary requirements.",
-    "type": "boolean"
-  },
-  "same_occupation_code": {
-    "description": "For role_change: whether the new role keeps the same occupation code; occupation-code changes may require a new CoS/application.",
-    "type": "boolean"
-  },
-  "same_salary_option_still_met": {
-    "description": "For salary_change: whether the original Skilled Worker salary option remains met after the change.",
-    "type": "boolean"
-  },
-  "total_weeks": {
-    "description": "For unpaid_or_reduced_pay_absence: total weeks of the absence at unpaid or reduced pay.",
-    "minimum": 0,
-    "type": "number"
-  },
-  "valid_exception": {
-    "description": "For an absence: whether a listed permitted-absence exception is established.",
-    "type": "boolean"
-  }
-}

removedInput schema / properties / payload / required
```
Removed value: -[
-  "event_type",
-  "route"
-]
```
addedInput schema / properties / payload / title
```
Added value: +"Payload"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "assess_change_impactDictOutput",
+  "type": "object"
+}

Changed26 schema fields changedSep 9, 2026

addedInput schema / properties / payload / properties / change_kind / description

Added value: +"For organisation_change or TUPE: the specific organisation or transfer change being assessed."

addedInput schema / properties / payload / properties / change_type / description

Added value: +"For merger_takeover: merger, takeover, or similar sponsor-organisation change type."

addedInput schema / properties / payload / properties / compelling_reason / description

Added value: +"For an absence: whether a compelling reason is established under the sponsor-duty rule."

addedInput schema / properties / payload / properties / consecutive_working_days / description

Added value: +"For unauthorised_absence: consecutive working days absent without authorisation."

addedInput schema / properties / payload / properties / delay_days / description

Added value: +"For worker_start_delay: days after the relevant Skilled Worker start-date trigger."

addedInput schema / properties / payload / properties / direction / description
```
Added value: +"Whether the salary change increases or decreases pay."
```

addedInput schema / properties / payload / properties / duties_unchanged / description

Added value: +"For TUPE or merger/takeover: whether the worker's duties remain unchanged."

changedInput schema / properties / payload / properties / event_type / description

Previous value: -"Sponsor change event category to assess."New value: +"Sponsor change event category to assess: absence; salary; role or occupation-code change; work-location or home-working change; delayed start; stopping sponsorship or worker departure; organisation change; TUPE transfer; or merger/takeover."

addedInput schema / properties / payload / properties / hybrid_only / description

Added value: +"For work_location_change: whether work remains hybrid with the main office unchanged."

addedInput schema / properties / payload / properties / new_client_site / description

Added value: +"For work_location_change: whether the worker has a new normal client site."

addedInput schema / properties / payload / properties / new_entity_has_relevant_licence / description
```
Added value: +"For merger_takeover: whether the new entity has the relevant sponsor licence."
```

addedInput schema / properties / payload / properties / new_main_office / description

Added value: +"For work_location_change: whether the worker has a new normal main office or branch."

addedInput schema / properties / payload / properties / new_sponsor_has_relevant_licence / description

Added value: +"For TUPE or merger/takeover: whether the receiving sponsor holds the relevant sponsor licence."

addedInput schema / properties / payload / properties / occasional_only / description

Added value: +"For work_location_change: whether the location change is only occasional and day-to-day."

addedInput schema / properties / payload / properties / old_entity_continues_trading / description

Added value: +"For merger_takeover: whether the old sponsor entity continues trading after the change."

addedInput schema / properties / payload / properties / permanent_remote / description

Added value: +"For work_location_change: whether the worker moves to permanent or full-time home working."

addedInput schema / properties / payload / properties / pre_registration_nurse_or_midwife / description

Added value: +"For salary_change: whether the worker is a pre-registration nurse or midwife covered by the modeled salary branch."

addedInput schema / properties / payload / properties / reason / description

Added value: +"Reason for stopping sponsorship or the worker's departure, or the relevant organisation-change reason."

addedInput schema / properties / payload / properties / revised_salary_meets_skilled_worker / description

Added value: +"For salary_change: whether the revised salary still meets a Skilled Worker salary basis."

addedInput schema / properties / payload / properties / role_eligible / description

Added value: +"For role_change: whether the proposed role is eligible under the Skilled Worker route."

changedInput schema / properties / payload / properties / route / description

Previous value: -"V0.1 supports Skilled Worker only; unsupported routes fail closed."New value: +"Visa route for the sponsor-duty decision. V0.1 supports Skilled Worker only; unsupported routes fail closed."

addedInput schema / properties / payload / properties / salary_requirements_met / description

Added value: +"For role_change: whether the proposed role and pay continue to meet applicable salary requirements."

addedInput schema / properties / payload / properties / same_occupation_code / description

Added value: +"For role_change: whether the new role keeps the same occupation code; occupation-code changes may require a new CoS/application."

addedInput schema / properties / payload / properties / same_salary_option_still_met / description

Added value: +"For salary_change: whether the original Skilled Worker salary option remains met after the change."

addedInput schema / properties / payload / properties / total_weeks / description

Added value: +"For unpaid_or_reduced_pay_absence: total weeks of the absence at unpaid or reduced pay."

addedInput schema / properties / payload / properties / valid_exception / description

Added value: +"For an absence: whether a listed permitted-absence exception is established."

First observedSep 8, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral detail beyond that: 'Use only facts explicitly supplied by the user; never infer or default missing compliance facts' and 'Pass omissions through so the deterministic engine can return INSUFFICIENT_INPUT.' It also discloses that the tool returns an evidence-linked decision, complementing the structured annotations well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the core purpose and then covering usage, behavioral constraints, and output. Every sentence earns its place with no filler or redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description need not detail return values, and it covers usage scenarios, omission behavior, and decision/next-action output adequately. The main gap is no explicit 'not for' boundary or sample payload shape, but the description is still sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema_description_coverage at 0% and a single opaque 'payload' object, the description must compensate, and it partially does. It explains that the payload contains only user-supplied facts, lists applicable change categories, and gives an example missing compliance fact (same_salary_option_still_met). It stops short of a full payload schema, but for a deliberately flexible payload this is substantive guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Check whether a specific employee/company change affects UK Skilled Worker sponsor duties.' It then enumerates concrete change types (salary, role, work-location, TUPE, merger, etc.), which clearly distinguishes it from siblings like licensing_source_status and list_supported_change_events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit 'Use for' list covering the relevant change scenarios, and it also says to pass omissions through rather than infer defaults. It does not name alternative tools for when-not/exclusion scenarios, so it has clear context but no explicit sibling routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RegEvidenceHub Sponsor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.