Skip to main content
Glama

MCP CPG Human in the Loop (HITL)

by io.github.greencore-solutions
OverviewDiscussionsAdmin

Server Details

Navigator for BPC Agentic Procurement

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
79.8% over 73 days
Last Tested
Transport
Streamable HTTP
URL
Repository
greencore-solutions/cpg-human-in-the-loop
GitHub Stars
0
Server Listing
MCP CPG Human in the Loop (HITL)

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct role: three create different types of tickets (RFQ, terms question, escalation) and one polls ticket status. The descriptions clearly delineate when to use each, leaving no real ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (check_rfq_status, request_terms, submit_rfq), but 'escalate' is a bare verb that breaks the pattern slightly. The names remain readable and predictable overall.

Tool Count5/5

Four tools is an appropriate size for a HITL ticket server: three ticket-creation paths and one status/answer polling function. No tool feels redundant or missing at this scope.

Completeness5/5

The toolset covers the full human-in-the-loop lifecycle: create tickets of all relevant types and retrieve status/answers. There are no dead ends — every creation tool returns a ticket ID that check_rfq_status can poll.

Tool Schema Changelog

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

  1. 4 tool updates
    • Changedcheck_rfq_status1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedescalate1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedrequest_terms1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedsubmit_rfq1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 3 tool updates
    • Changedescalate1 field changed
      • removedInput schema / properties / agent_card
        Removed value: -{
-  "description": "Optional: your A2A agent card URL or hostname — verified at task acceptance (JWS over RFC 8785). VERIFIED handshakes enter the guest book at gsc-handshake.ai by name.",
-  "maxLength": 300,
-  "type": "string"
-}
    • Changedrequest_terms1 field changed
      • removedInput schema / properties / agent_card
        Removed value: -{
-  "description": "Optional: your A2A agent card URL or hostname — verified at task acceptance (JWS over RFC 8785). VERIFIED handshakes enter the guest book at gsc-handshake.ai by name.",
-  "maxLength": 300,
-  "type": "string"
-}
    • Changedsubmit_rfq1 field changed
      • removedInput schema / properties / agent_card
        Removed value: -{
-  "description": "Optional: your A2A agent card URL or hostname — verified at task acceptance (JWS over RFC 8785). VERIFIED handshakes enter the guest book at gsc-handshake.ai by name.",
-  "maxLength": 300,
-  "type": "string"
-}
  3. 3 tool updates
    • Changedescalate1 field changed
      • addedInput schema / properties / agent_card
        Added value: +{
+  "description": "Optional: your A2A agent card URL or hostname — verified at task acceptance (JWS over RFC 8785). VERIFIED handshakes enter the guest book at gsc-handshake.ai by name.",
+  "maxLength": 300,
+  "type": "string"
+}
    • Changedrequest_terms1 field changed
      • addedInput schema / properties / agent_card
        Added value: +{
+  "description": "Optional: your A2A agent card URL or hostname — verified at task acceptance (JWS over RFC 8785). VERIFIED handshakes enter the guest book at gsc-handshake.ai by name.",
+  "maxLength": 300,
+  "type": "string"
+}
    • Changedsubmit_rfq1 field changed
      • addedInput schema / properties / agent_card
        Added value: +{
+  "description": "Optional: your A2A agent card URL or hostname — verified at task acceptance (JWS over RFC 8785). VERIFIED handshakes enter the guest book at gsc-handshake.ai by name.",
+  "maxLength": 300,
+  "type": "string"
+}
  4. 4 tool updates
    • First observedcheck_rfq_status
    • First observedescalate
    • First observedrequest_terms
    • First observedsubmit_rfq

Related MCP Connectors

Related MCP Servers

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.

Resources