Skip to main content
Glama
Sign In
jolly-tur-mcp

jolly-tur-mcp

by mohammad-abbasi-sh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jolly-tur-mcp

No user-submitted related servers found.

    Related Servers

    • Hotelbeds MCP Server

      karanrao
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search hotel availability, validate rates, create and retrieve bookings, simulate or execute cancellations, and browse destinations and hotel content through the Hotelbeds Booking and Content APIs. Includes a surface-and-reconfirm booking flow that re-validates live prices with a tolerance before confirming.
      9
      MIT

    • biletall-mcp

      mohammad-abbasi-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only search of Turkish bus and flight tickets on biletall.com, including routes, journeys, prices, price statistics, popular routes, and location lookup through MCP tools.
      MIT

    • Core MCP

      guestitab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables destination discovery, stay search, detailed listing reads, and dated price comparisons through MCP tools and an interactive widget, while directing booking to the host website.
      MIT

    • webhotelier-mcp

      gabrielnika
      F
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that lets AI assistants query the WebHotelier REST API for live hotel data, including property info, room availability, rates, calendars, and offers via natural language tools.
      8
      -
    Deploy Server
    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

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a distinct operation: city-level search, single-hotel detail lookup, and campaign listing. There is no plausible way to confuse them, and the search-to-detail handoff (hotel_slug from search results) is explicitly documented.

    Naming Consistency5/5

    All three tools use the same jolly_<verb>_<noun> convention (jolly_search_hotels, jolly_get_hotel, jolly_list_campaigns). The server prefix is applied uniformly and verbs are used consistently for their action type.

    Tool Count4/5

    Three tools is on the thin side, but for a read-only hotel discovery server each tool earns its place and nothing is redundant. A small set of extra tools (e.g. destination/availability lookup) would round it out without bloat.

    Completeness4/5

    The core read-only lifecycle is covered: find hotels by city, drill into a hotel, and surface current promotions. Gaps remain around room/availability details and booking or filtering beyond name and city, but agents can work around these for search-oriented tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources