Skip to main content
Glama

LiveDataLink

by io.github.blackboxfoundry
OverviewDiscussionsAdmin

ok_wells_search

Read-onlyIdempotent

Search Oklahoma oil & gas wells by county, operator, API number, and/or well type using the Oklahoma Corporation Commission (OCC) RBDMS well database (keyless public record). Unlike a pure map layer, this returns the OPERATOR, well status, well type (OIL/GAS/DRY/etc.), well name, county, and location for each match, plus the total matching count and a by-operator/by-type breakdown. Use it for 'who operates wells in county X', 'how many wells does operator Y have', or an operator's well portfolio. Oklahoma covers the Anadarko Basin / SCOOP / STACK plays. At least one of county, operator, or api is recommended to narrow the search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiNoAPI well number (digits; non-digits are ignored).
limitNoMax well records to return (default 25, max 100). The total matching count is always reported.
countyNoOklahoma county name (e.g. 'Canadian', 'Kingfisher', 'Grady'). Matched case-insensitively.
operatorNoOperator name or fragment (e.g. 'Chesapeake', 'Devon'). Substring, case-insensitive.
well_typeNoFilter by well type: OIL, GAS, DRY, SWD (saltwater disposal), etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the safety profile is known. The description adds useful context beyond that: it identifies the source as a keyless public record (no auth) and enumerates the exact fields returned (operator, status, type, name, county, location) plus the total count and by-operator/by-type breakdown.

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?

Front-loaded with purpose and source, then returns, then usage. Well organized, but the play-name sentence (Anadarko Basin / SCOOP / STACK) is flavor rather than operational guidance, pushing it slightly past strict conciseness.

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 correctly carries the return-value burden and does so thoroughly (per-well fields plus aggregate count and breakdown). Annotations handle safety and keyless access is stated, leaving no material gap for an agent to call it correctly.

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?

With 100% schema description coverage, the baseline is 3, and the schema documents every parameter including value examples and casing behavior. The description adds a genuinely non-schema insight: that all five params are optional but at least one of county/operator/api is recommended to narrow results, plus the well_type value hints.

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 (Search) and resource (Oklahoma oil & gas wells), names the authoritative data source (OCC RBDMS), and explicitly lists the filter dimensions (county, operator, API number, well type). The Oklahoma scope is enough to distinguish it from the Texas sibling tx_wells_near without opening either 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?

Provides concrete example queries ('who operates wells in county X', 'how many wells does operator Y have') that map directly to intended use cases, and advises narrowing with at least one of county/operator/api. It stops short of naming an alternative tool or an explicit when-not-to-use, so it falls just below the top band.

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

All LiveDataLink 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