WellState Labs SB 1150 Screening (read-only)

Screen a surety book of principals

screen_book

Read-onlyIdempotent

Screens a surety broker's book of up to 25 Railroad Commission of Texas operator numbers (principals) with the surety-book-v1 semantics: one row per principal in request order with the P-5 letter verbatim (A labelled active, D delinquent, any other letter unlabelled), claims on file, AFFECTED on the evaluation date, approaching within 24 months, the Commission-published cost proxy with the priced claim count and the rate label read from the publication's cost_rate_basis (a fiscal year's Commission rates, or the publication's own label verbatim when it establishes no table year), unpriced claims, the Full Wellbore flagged counts (a cross-check only) and the 16 TAC §3.78 blanket floor from inactive wells only (a lower bound, not a bond amount). Book totals are given only where a sum is valid; unpriced claims and the floors are NOT_SUMMED, with the reason. Wellbores two principals of the book both claim are disclosed with the claims and cost the totals count more than once. A principal not in the publication refuses the whole book rather than leave a row out.

Input Schema

Name	Required	Description	Default
`operator_numbers`	Yes	1-25 six-digit Railroad Commission of Texas operator numbers as strings, each once (e.g. ["276959", "760218"]). The rows keep this order.

Output Schema

Name	Required	Description	Default
`rows`	Yes
`terms`	Yes
`totals`	Yes
`overlap`	Yes
`p5_note`	Yes
`boundary`	Yes
`reliance`	Yes
`cost_note`	Yes
`count_unit`	Yes
`iwar_as_of`	Yes
`principals`	Yes
`rate_basis`	Yes
`publication`	Yes
`format_version`	Yes
`evaluation_date`	Yes
`publication_root`	Yes
`blanket_floor_note`	Yes
`within_24_months_by`	Yes
`full_wellbore_crosscheck_note`	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",
-  "format_version",
-  "principals",
-  "count_unit",
-  "evaluation_date",
-  "within_24_months_by",
-  "iwar_as_of",
-  "rate_basis",
-  "cost_note",
-  "p5_note",
-  "blanket_floor_note",
-  "full_wellbore_crosscheck_note",
-  "reliance",
-  "rows",
-  "totals",
-  "overlap",
-  "publication"
-]New value: +[
+  "boundary",
+  "terms",
+  "publication_root",
+  "format_version",
+  "principals",
+  "count_unit",
+  "evaluation_date",
+  "within_24_months_by",
+  "iwar_as_of",
+  "rate_basis",
+  "cost_note",
+  "p5_note",
+  "blanket_floor_note",
+  "full_wellbore_crosscheck_note",
+  "reliance",
+  "rows",
+  "totals",
+  "overlap",
+  "publication"
+]

First observedOct 30, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The description goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing row structure, P-5 letter handling, claims and cost semantics, NOT_SUMMED totals, cross-check caveats, shared-wellbore double counting, and the all-or-nothing refusal when a principal is missing. These details materially affect how an agent should interpret and trust the output.

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?

The purpose is front-loaded and nearly every clause carries specific semantic weight for a complex batch tool. However, the description is one very long run-on sentence, and some phrasing reiterates schema facts like the 25-principal limit and order preservation, making it slightly harder to parse than necessary.

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?

Given the tool's complexity, the description covers the critical behavioral edge cases an agent needs: row ordering, missing-principal refusal, unpriced and floor NOT_SUMMED totals, shared-wellbore double counting, and the non-bond nature of the §3.78 floor. The output schema is available for return-value structure, so no further detail is required.

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 parameter is already fully documented, but the description adds meaning by stating that rows preserve request order and that any principal outside the publication causes the entire book to be refused. This goes beyond the schema's syntactic constraints.

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

Purpose4/5

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

The description states a specific verb ('Screens') and resource ('a surety broker's book of up to 25 Railroad Commission of Texas operator numbers'), making the batch-book scope clear. It does not explicitly name or contrast with sibling tools like screen_operators, so sibling differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

The description explains what the tool does but gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer that this is the batch-screening option versus single-operator siblings from the phrase 'book of up to 25' alone.

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?