WellState Labs SB 1150 Screening (read-only)

List an operator's wellbores

list_operator_wells

Read-onlyIdempotent

Lists one operator's wellbore claims from the publication, filtered by outcome (AFFECTED, APPROACHING or ALL; default AFFECTED) and sorted by Commission-published plugging cost descending, unpriced wellbores last, then by API number. Returns one page of at most 100 rows plus the number matching and the Commission-published cost total over all matching rows (the same on every page). When more rows remain, next_cursor is set: pass it back as cursor, with the same operator_number and outcome, for the next page. A cursor is bound to the publication root that issued it.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum rows on this page, 1-100. Default 25.
`cursor`	No	next_cursor from the previous page, unchanged. Omit for the first page. Refused when it was issued for another publication root, operator or outcome.
`outcome`	No	AFFECTED: affected at the evaluation date. APPROACHING: not affected then but affected by 2042-09-01 (compliance-plan horizon). ALL: every claim. Default AFFECTED.	AFFECTED
`operator_number`	Yes	Six-digit Railroad Commission of Texas operator number, with leading zeros (e.g. 276959).

Output Schema

Name	Required	Description
`link`	Yes
`sort`	Yes
`terms`	Yes
`wells`	Yes
`offset`	Yes	Position of this page's first row in the full sorted listing, from 0.
`boundary`	Yes
`returned`	Yes
`truncated`	Yes	True when rows remain after this page.
`next_cursor`	Yes	Pass as cursor for the next page; null on the last page.
`display_name`	Yes
`outcome_filter`	Yes
`total_matching`	Yes
`operator_number`	Yes
`publication_root`	Yes
`matching_unpriced_count`	Yes
`matching_commission_published_total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

addedOutput schema / properties / terms

Added value: +{
+  "const": "https://mcp.wellstatelabs.com/terms",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "boundary",
-  "publication_root",
-  "operator_number",
-  "display_name",
-  "outcome_filter",
-  "sort",
-  "total_matching",
-  "returned",
-  "truncated",
-  "offset",
-  "next_cursor",
-  "matching_commission_published_total",
-  "matching_unpriced_count",
-  "wells",
-  "link"
-]New value: +[
+  "boundary",
+  "terms",
+  "publication_root",
+  "operator_number",
+  "display_name",
+  "outcome_filter",
+  "sort",
+  "total_matching",
+  "returned",
+  "truncated",
+  "offset",
+  "next_cursor",
+  "matching_commission_published_total",
+  "matching_unpriced_count",
+  "wells",
+  "link"
+]

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, and the description layers on real behavioral detail: a 100-row page cap, totals that repeat on every page, next_cursor presence signalling more rows, and the constraint that a cursor is bound to the issuing publication root and refused otherwise. That is more than the structured fields convey.

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

Conciseness4/5

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

Ordering and paging facts are front-loaded and every sentence carries information, but the opening sentence bundles filter, sort, and tie-break rules into one long clause, and the cursor-binding sentence partly duplicates the cursor schema description.

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?

With an output schema present, return-shape explanation is optional, yet the description still tells the agent what comes back (rows, match count, cost total) and how to continue paging. Nothing needed to call this correctly is missing.

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; the description earns above that by explaining the outcome semantics (APPROACHING means affected by 2042-09-01) and the sorting consequences of the default limit. Cursor reuse rules are restated from the schema, so it does not reach 5.

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?

The description names a specific verb and resource ('Lists one operator's wellbore claims from the publication') and pins down scope, filters, and sort order. An agent can distinguish it from siblings like get_well or get_operator_exposure without opening a schema.

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

Usage Guidelines4/5

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

It gives clear operational guidance: default outcome AFFECTED, how to page (pass next_cursor back as cursor with the same operator_number and outcome), and that ALL means every claim. It stops short of stating when to prefer this over get_operator_exposure or screen_book, so it is clear context but not full alternative routing.

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

All WellState Labs SB 1150 Screening (read-only) tools Inspect

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

Need Help?