Skip to main content
Glama

Server Details

Workplace Recycling Rules: the site's own MCP server — checker, enquiry (enquiry = a human...

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 6 tools

Disambiguation4/5

The set splits cleanly into two domains: the 'checker' decision-guide tools and the 'enquiry' submission tools. Within the checker group, checker_tree overlaps somewhat with checker_start + checker_answer since it exposes the whole guide for end-to-end reasoning, but each still has a distinguishable role. enquiry_describe (meta/consent), enquiry_fields (schema) and submit_enquiry (action) are clearly separable.

Naming Consistency4/5

Names are grouped by domain prefix (checker_start, checker_answer, checker_tree; enquiry_describe, enquiry_fields), which is predictable and readable. submit_enquiry deviates slightly by using a verb-first form rather than the enquiry_ prefix, but it still fits the domain vocabulary, so the deviation is minor.

Tool Count4/5

Six tools is a sensible, well-scoped count for a decision guide plus a form-submission flow. Each tool has a distinct role, though checker_tree is arguably a convenience aggregation of the start/answer pair, making it just slightly redundant rather than excessive.

Completeness4/5

The surface covers the full lifecycle: starting the checker, advancing questions, dumping the whole tree, describing the enquiry, listing its fields, and a two-step consent-gated submit. The main gap is the absence of any status/retrieval tool (e.g. checking an already-submitted enquiry), which agents could work around but would expect in a submission flow.

Available Tools

6 tools
checker_answerAnswer a question, get the next stepAInspect

Given a question id and the chosen option (its choice index), return the next question or the final verdict.

Inputs: choice (required), question (required).

checker_startStart: Workplace recycling duty checkerAInspect

The first question of the Workplace recycling duty checker decision guide.

Inputs: no named parameters.

checker_treeThe whole decision treeAInspect

Every question, option and verdict of the Workplace recycling duty checker guide, for reasoning end to end.

Inputs: no named parameters.

enquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)AInspect

Read first. States plainly what submit_enquiry does on Workplace Recycling Rules: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

Inputs: no named parameters.

enquiry_fieldsThe questions the enquiry asksAInspect

Every field of the Workplace Recycling Rules enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

Inputs: no named parameters.

submit_enquirySubmit an ENQUIRY to human providers (two steps; not a purchase)AInspect

Submits an enquiry to Workplace Recycling Rules — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three relevant waste management companies, chosen by Workplace Recycling Rules, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Inputs: answers (required), consent (required), confirmation.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      An MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.
      5
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This local MCP server lets an AI agent open a session, post items and questions for a developer to review on a local page, hold threaded conversations about each item, and wait for events until every item has a verdict. It enforces the workflow rules itself, blocking approval while questions are open and counting a verdict only for the revision on screen.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables employees to ask IT questions, receive evidence-backed answers, and trigger traceable work orders or escalations through authenticated MCP tools. It also supports status checks, durable action jobs, and auditable work-order, Excel ledger, and escalation workflows.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for grounded, cited AI: answers questions from live web sources, verifies claims, fact-checks documents, searches and reads URLs, summarises, classifies, and extracts fields, with usage tracking and status.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources