Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bsee_hpht_regulatory_classifierB

Classifies Gulf of Mexico deepwater wells under BSEE NTL 2019-G03 and API 17TR8 guidelines, determining whether 20,000 PSI Tier-1 regulations, Independent Third-Party (I3P) verification, and Certified Verification Agent (CVA) approvals are legally triggered.

lookup_gom_protraction_areaA

Looks up BOEM Outer Continental Shelf (OCS) deepwater protraction areas in the Gulf of Mexico (MC, GC, WR, KC, AC, VK, AT), returning water depths, geological Wilcox/Miocene trends, and flagship host platform hubs.

estimate_tieback_economicsA

Evaluates subsea tieback capital expenditures (CAPEX), breakeven oil prices ($25-$35/bbl), and flow assurance distance thresholds versus standalone greenfield floating production units (FPUs).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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.