Skip to main content
Glama

texas-rrc-wellbores

Server Details

Texas RRC oil & gas wellbores: API numbers, completion dates, depth, plug status

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are cleanly separated: describe_texas_wellbores returns metadata/schema with no records, while search_texas_wellbores returns actual rows. The description even instructs the caller to invoke describe first, eliminating any chance of misselection.

Naming Consistency5/5

Both names follow the same verb_noun snake_case pattern (describe_/search_) with a consistent domain suffix (texas_wellbores). The convention is predictable and unambiguous.

Tool Count3/5

Two tools is thin even for a read-only dataset service; the surface is essentially one discovery call plus one query call. It is defensible for a narrowly scoped lookup API, but leaves no room for variants such as single-record fetch or field-level filtering.

Completeness3/5

Read-only search plus schema description covers the core access pattern, and search supports several useful filters. However, there is no lookup-by-API-number/identity fetch, no aggregation or count operation, and the describe tool itself admits parts of the source are not yet parsed, so the surface is notably partial.

Available Tools

2 tools
describe_texas_wellboresDescribe the Texas RRC wellbore datasetAInspect

Free, no API key required. Describes the Texas Railroad Commission wellbore identity dataset decoded from RRC's EBCDIC mainframe corpus: the exact fields available, row count, freshness, pricing, and which parts of the source are NOT yet parsed. Returns no records. Call this before search_texas_wellbores.

Inputs: no named parameters.

search_texas_wellboresSearch Texas RRC wellboresAInspect

Search Texas oil and gas wellbore identities by district, county, API number, plugged status, orphan-well hold, completion date range or minimum depth. FREE tier: up to 25 real decoded rows per call with no API key, so you can judge the data before paying. Asking for more than 25 rows or using offset requires a key and otherwise returns a payment_required error carrying a checkout URL.

Inputs: limit, county, offset, plugged, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables live querying of oil & gas and geothermal well data from state regulator ArcGIS services, including searchable well records, operators, nearby wells, and raw queries, plus DOE GDR and Global Energy Monitor lookups.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search U.S. hydraulic fracturing disclosure records — well-level frac job details (operator, API number, location, dates, base fluid volumes) and the disclosed chemical additives per job — by state, county, operator, or API number, plus lookups of where a given chemical has been used by CAS number. Responses include source, license, and coverage-window metadata so callers can distinguish missing data from out-of-window disclosures.
      79 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Model Context Protocol (MCP) server for Gulf of Mexico deepwater intelligence: BSEE NTL 2019-G03 HPHT regulatory classification, API 17TR8 20,000 PSI qualification mandates, BOEM OCS protraction area intelligence, and subsea tie-back economic heuristics.
      3
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and querying Texas open data from data.texas.gov via the Socrata SoQL API, supporting dataset discovery, filtering, and metadata retrieval without an API key.
      159 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources