Skip to main content
Glama
Sign In

Fracfocus

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Frac Wells

frac_wells
Read-onlyIdempotent

Hydraulic fracturing job disclosures (wells) from FracFocus, the national frac-chemical disclosure registry -- filter by state, county, and/or operator name (operator matches as a substring, case-insensitive). Returns each well's API number, operator, well name, location, job dates, and base fluid volumes, newest job first. Covers FracFocus's full disclosure history (back to its earliest submissions, most of it from 2011 on). Pass the API number from a result into frac_chemicals to get that job's chemical ingredient list. At least one of state, county, or operator is required -- an unscoped scan of ~250k disclosures is not supported.

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, 1-200. Default 50. A truncated response carries truncated:true, total_matching, and a hint for narrowing.
stateNoUS state name, e.g. "Texas" (full name, case-insensitive; FracFocus stores state as a name, not a postal code).
countyNoCounty name, e.g. "Martin". Case-insensitive exact match.
offsetNoPagination offset. Default 0.
operatorNoOperator name, substring match, case-insensitive, e.g. "Pioneer".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent/openWorld annotations, the description discloses matching semantics (operator substring, case-insensitive), the returned field set and sort order (newest job first), the historical coverage of the dataset, and the prohibition on unscoped scans. That is rich operational context an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what the tool is, then filters, then return shape, then cross-tool handoff, then the hard constraint. Four dense sentences with no filler; each one carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-value burden and does so (API number, operator, well name, location, job dates, base fluid volumes, newest-first ordering). Combined with the limit/truncation notes in the schema, an agent has everything needed to call and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a constraint the schema does not encode: the schema lists 0 required parameters, yet at least one of state/county/operator is actually mandatory. It also restates the substring/case-insensitive matching behavior that governs operator results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (hydraulic fracturing job disclosures from FracFocus) plus scope (state/county/operator filters) and distinguishes itself from the sibling frac_chemicals by routing chemical lookups there. An agent can identify this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the mandatory scope condition ('at least one of state, county, or operator is required -- an unscoped scan of ~250k disclosures is not supported') and names the alternative tool plus the exact handoff key (API number into frac_chemicals). When-to-use and when-not-to-use are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fracfocus toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources