Skip to main content
Glama

BookingTruth Booking Assurance

by com.bookingtruth
OverviewDiscussionsAdmin

Server Details

Verifies travel bookings against supplier-authoritative evidence; honest UNKNOWN verdicts.

Glama couldn't complete the latest health check. 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
33.4% over 21 days
Last Tested
Transport
Streamable HTTP
URL
Server Listing
bookingtruth

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: booking_check parses documents and returns a verdict, while supplier_coverage lists supported suppliers. There is no overlap in action or resource, so an agent can easily select the right tool.

Naming Consistency4/5

Both names use snake_case and are descriptive, but they follow slightly different patterns (noun_verb vs noun_noun). This is a minor deviation from a fully consistent convention, though still readable and predictable.

Tool Count3/5

Two tools is thin for a booking assurance service, even if they cover the core check-and-list workflows. The surface feels minimal and could benefit from at least one more operation, such as retrieving a specific check result or supplier detail.

Completeness4/5

For a read-only assurance service, booking_check and supplier_coverage cover the essential workflows: verifying a booking and knowing which suppliers are supported. Minor gaps exist, such as no tool to retrieve historical check results or detailed proof packets separately, but agents can work around them.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedbooking_check1 field changed
      • changedOutput schema / properties / bookings / items / properties / proof_url / description
        Previous value: -"URL of the citable proof packet for this verdict."New value: +"URL of the citable proof packet (present only on CONFIRMED verdicts)."
  2. 2 tool updates
    • Changedbooking_check1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "bookings": {
+      "description": "Reconciled bookings with verdicts.",
+      "items": {
+        "properties": {
+          "booking_id": {
+            "description": "Stable booking identifier (e.g. conf:ABC123).",
+            "type": "string"
+          },
+          "contradictions": {
+            "description": "Logged conflicts across sources.",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "evidence_tier": {
+            "description": "Highest evidence tier behind the verdict (0-6).",
+            "type": "integer"
+          },
+          "indicated_state": {
+            "description": "What the documents suggest when the evidence bar is not met.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "needs_primary_check": {
+            "description": "True when a supplier-side lookup is the only safe way to resolve.",
+            "type": "boolean"
+          },
+          "proof_url": {
+            "description": "URL of the citable proof packet for this verdict.",
+            "type": "string"
+          },
+          "state": {
+            "description": "Verdict. CONFIRMED only on supplier-authoritative evidence.",
+            "enum": [
+              "confirmed",
+              "held",
+              "pending",
+              "cancelled",
+              "unknown"
+            ],
+            "type": "string"
+          },
+          "supplier": {
+            "description": "Detected supplier (united, expedia, disney, ...).",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • Changedsupplier_coverage1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "properties": {
+    "coverage": {
+      "description": "Per-supplier parser/lookup coverage.",
+      "items": {
+        "properties": {
+          "email_parse": {
+            "type": "boolean"
+          },
+          "receipt_artifacts": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "status": {
+            "enum": [
+              "seeded",
+              "planned"
+            ],
+            "type": "string"
+          },
+          "supplier": {
+            "type": "string"
+          },
+          "tier1_lookup": {
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. 2 tool updates
    • First observedbooking_check
    • First observedsupplier_coverage

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