Skip to main content
Glama
openfantasymap

odh-mcp-server

by openfantasymap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to odh-mcp-server

No user-submitted related servers found.

    Related Servers

    • Fast MCP Server

      pablo-dutra6
      F
      license
      Not graded
      quality
      C
      maintenance
      A modular MCP server built with FastAPI, exposing tools via HTTP endpoints with SSE streaming responses.
      -

    • FastMCP

      wanderingnature
      A
      license
      Not graded
      quality
      D
      maintenance
      FastMCP is a comprehensive MCP server allowing secure and standardized data and functionality exposure to LLM applications, offering resources, tools, and prompt management for efficient LLM interactions.
      3
      MIT

    • got-cosy-mcp

      perwinroth
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing cosiness scores for about 6,300 independent hotels, with tools to find hotels by city/country and retrieve detailed feeling data.
      2
      MIT

    • mcp_local_server

      sarthakdeshmukh0770-jpg
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight local MCP server built with FastMCP for exposing custom tools to MCP-compatible clients. Enables local development and testing of MCP tools and resources.
      1
      -

    • Basic MCP

      nimishgautam
      A
      license
      Not graded
      quality
      D
      maintenance
      A simple MCP server built with FastMCP for experimentation and learning purposes. Includes basic web tools like article fetching and serves as a human-readable template for building custom MCP servers.
      AGPL 3.0
    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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: set_world establishes context, describe_world explains it, and the three find_* tools query for accommodations, events, and gastronomy separately. Even though they share parameters like near and radius_m, the entity types are clearly different, so an agent can easily select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: set_world, describe_world, find_accommodations, find_events, find_gastronomy. The verbs (set, describe, find) are clear and the nouns are specific, making the pattern predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of exploring hospitality and tourism data in a world context. Each tool earns its place: world management (set, describe) and three distinct search types (accommodation, events, gastronomy). No redundancy or bloat.

    Completeness5/5

    The server's domain is read-only exploration of world-based hospitality data, and it covers the core workflow: set the world to establish context, understand what data is available via describe_world, and then search for the three primary POI types. There are no obvious dead ends, and all CRUD operations beyond reading are outside the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources