RegEvidenceHub Waste

waste_rule_preflight

Read-onlyIdempotent

FREE GENERAL ENTRY TOOL for a CURRENT England waste operation when the regulatory route is still uncertain. Provide nation, role, one or more modelled activities, and any known site/waste/authorisation facts. Returns a deterministic route, missing facts, findings, evidence and next actions; it is read-only and does not submit anything. Do NOT use when the question is specifically carrier/broker/dealer registration, DWT receiving-site readiness, or a current-vs-proposed permit change; use the corresponding narrow tool instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scenario`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedInput schema / $defs / WasteRuleScenario / properties / nation / description

Previous value: -"UK nation for the operation. This public preflight currently supports England only and never infers jurisdiction."New value: +"UK nation for the operation. This service currently supports England only and never infers jurisdiction."

Changed5 schema fields changedSep 24, 2026

addedInput schema / $defs

Added value: +{
+  "WasteRuleScenario": {
+    "additionalProperties": false,
+    "properties": {
+      "activities": {
+        "description": "One or more modelled activities. Do not invent waste codes or hazardous status from an activity label.",
+        "items": {
+          "enum": [
+            "produce_controlled_waste",
+            "transport_waste",
+            "arrange_waste",
+            "receive_waste",
+            "store_waste",
+            "treat_recover_dispose_waste"
+          ],
+          "type": "string"
+        },
+        "title": "Activities",
+        "type": "array"
+      },
+      "authorisation_status": {
+        "anyOf": [
+          {
+            "enum": [
+              "permit",
+              "exemption",
+              "licence",
+              "none",
+              "other"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Current receiving/operator authorisation when known. Do not infer permit or exemption status.",
+        "title": "Authorisation Status"
+      },
+      "hazardous_status": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Whether hazardous waste is involved, only when explicitly known from the user's facts; otherwise leave null.",
+        "title": "Hazardous Status"
+      },
+      "nation": {
+        "anyOf": [
+          {
+            "const": "England",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "UK nation for the operation. This public preflight currently supports England only and never infers jurisdiction.",
+        "title": "Nation"
+      },
+      "role": {
+        "anyOf": [
+          {
+            "enum": [
+              "producer",
+              "carrier",
+              "broker",
+              "dealer",
+              "receiver",
+              "operator"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Primary waste role. Use receiver/operator for sites taking or operating on waste; carrier/broker/dealer for movement or arranging roles.",
+        "title": "Role"
+      },
+      "site_location": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Site or sufficiently precise operating location in England when location matters to the route.",
+        "title": "Site Location"
+      },
+      "waste_types": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "User-supplied waste types or codes. Do not infer EWC codes from free text.",
+        "title": "Waste Types"
+      }
+    },
+    "title": "WasteRuleScenario",
+    "type": "object"
+  }
+}

addedInput schema / properties / scenario / $ref
```
Added value: +"#/$defs/WasteRuleScenario"
```
removedInput schema / properties / scenario / additionalProperties
```
Removed value: -true
```
removedInput schema / properties / scenario / title
```
Removed value: -"Scenario"
```
removedInput schema / properties / scenario / type
```
Removed value: -"object"
```

First observedSep 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark readOnlyHint=true, idempotentHint=true, and destructiveHint=false; the description reinforces this by saying 'it is read-only and does not submit anything.' It adds value beyond annotations by describing the deterministic route, missing facts, findings, evidence, and next actions returned.

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?

Three sentences with no filler: purpose and triggering condition, required inputs, output behavior, and exclusions. It front-loads the core scope and routes to alternatives in a tight, efficient paragraph.

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

Completeness5/5

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

For a read-only preflight tool with an output schema and a sibling family, the description covers purpose, jurisdiction, usage exclusions, input summary, and output behavior. Nothing needed to select or call the tool correctly is missing.

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

Parameters3/5

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

With top-level schema description coverage at 0%, the description must compensate, and it names the key inputs: nation, role, one or more modelled activities, and known site/waste/authorisation facts. However, it does not explain codelists, null/default behavior, or the 'do not infer' warnings, so compensation is partial.

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 'FREE GENERAL ENTRY TOOL for a CURRENT England waste operation when the regulatory route is still uncertain,' clearly stating the operation, jurisdiction, timing, and trigger. It also distinguishes itself from sibling tools by naming specific exclusions and directing to the corresponding narrow tools.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool ('when the regulatory route is still uncertain') and lists three concrete exclusions: carrier/broker/dealer registration, DWT receiving-site readiness, and current-vs-proposed permit change. The instruction to use the corresponding narrow tool is unambiguous.

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

All RegEvidenceHub Waste 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.