Skip to main content
Glama
tudadada

gom-deepwater-radar

by tudadada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to gom-deepwater-radar

No user-submitted related servers found.

    Related Servers

    • petro-mcp

      tallihealth
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives LLMs access to 70 petroleum engineering tools for well logs, decline curves, PVT, drilling, economics, and more.
      1
      MIT

    • opendtect-mcp

      Wzhang3912
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server that drives OpendTect headlessly for SEG‑Y import, 3D horizon auto‑tracking, ASCII export, and horizon‑agreement scoring.
      2
      MIT

    • petropt/petro-mcpprivate

      petropt
      A
      license
      B
      quality
      B
      maintenance
      MCP server that gives LLMs access to petroleum engineering data and tools. Parse well logs, query production data, fit decline curves, calculate EUR, and run nodal analysis -- all through natural language with any MCP-compatible AI assistant.
      83
      1
      MIT

    • worldmonitor-mcp

      mahimn01
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server wrapping worldmonitor global intelligence dashboard, exposing 140 tools across 32 services for live market, geopolitical, military, cyber, climate, and supply chain data.
      MIT

    • Globalpulse-MCP

      gpavan1992
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides real-world intelligence including macroeconomics, climate, disasters, aviation, trade, and country data from globally trusted open APIs with no proprietary subscriptions required.
      11
      29 npm
      1
      MIT
    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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: regulatory classification, protraction-area lookup, and tieback economics. There is no overlap in the resource or action being targeted, so an agent can easily select the right tool.

    Naming Consistency4/5

    All names use snake_case and are descriptive, but the first tool lacks an action verb and instead leads with an agency/acronym, while the other two follow a verb-noun pattern. The inconsistency is minor and does not impair readability.

    Tool Count5/5

    Three tools are well-scoped for a focused deepwater analysis server, and each tool covers a distinct analytical dimension. The count is small but not trivially thin, given the specificity of the domain.

    Completeness3/5

    The surface covers regulatory classification, geological area lookup, and tieback economics, but it lacks direct well, platform, pipeline, or production-data access that a 'deepwater radar' user might reasonably expect. These gaps are notable though workable for the three supported workflows.

    Resources