Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Hotel & Resort Direct Booking Engine & OTA Spy

spy_hotel_direct_booking_ota_parity
Read-onlyIdempotent

Detect hotel booking engines, OTA widgets, and GM/sales contacts across domains to assess direct-booking and OTA parity gaps.

Instructions

Detect Cloudbeds, SynXis, Mews, SiteMinder, Booking.com/Expedia widgets, and hospitality GM/sales contacts across hotel websites ($0.80/1k).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domains": "<domains>"
    },
    "name": "spy_hotel_direct_booking_ota_parity"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesHotel, resort, or boutique hospitality domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds a genuinely useful trait outside the annotations: the $0.80/1k pricing, which lets an agent reason about cost before batching many domains. It does not describe return shape or whether detections and contacts come back merged.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the verb leads and the price is appended last where it belongs. It is slightly list-dense, packing six vendors plus a contact type into one clause, which makes it scan as a keyword dump rather than prose.

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

Completeness3/5

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

For a one-parameter, no-output-schema tool, the description covers what is detected and the cost, and annotations cover safety. It omits how results are returned (one record per domain? merged tech + contact payload?) and whether a domain with no detected stack returns empty versus erroring, which matters for a scan tool.

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?

Schema coverage is 100% and the single parameter is already described as "Hotel, resort, or boutique hospitality domains." The description repeats this as "across hotel websites" without adding batch-size limits, domain-format expectations, or behavior on non-hospitality input. Baseline 3 is correct when the schema does the work.

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

Purpose4/5

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

Names a specific verb ("Detect") and enumerates concrete detection targets: Cloudbeds, SynXis, Mews, SiteMinder, Booking.com/Expedia widgets, plus GM/sales contacts. Scope is bounded to hotel websites, which separates it from the generic B2B lead-gen siblings. It stops short of naming an alternative tool, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to a sibling for adjacent cases (e.g. general contact enrichment or Google Maps lead scraping). The only implicit signal is that inputs must be hospitality domains. An agent must infer the use case entirely from the target list.

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