Govparse Government Data Gateway

msha_mines_search

Which mines and quarries operate in a market, and who runs them? Search the MSHA Mines data set — every coal and metal/non-metal mine under MSHA jurisdiction (NAICS-21 operators that are OSHA-exempt and invisible elsewhere) — by operator, mine name, state, county, commodity, canvass, coal_metal, mine type, status, active-only, or status date (since). Returns the mine, its operator (entity-resolved) and controller, commodity, employees, and status. MSHA public-domain records. [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	status_dt \| mine_name \| employees :asc\|:desc. Default status_dt:desc.
`limit`	No	Max rows (default 25, cap 100).
`since`	No	Current-status date on/after this date (YYYY-MM-DD) — surfaces newly-statused mines.
`state`	No	State code(s), CSV.
`active`	No	true = currently-active mines only.
`county`	No	County name fragment.
`offset`	No	Rows to skip.
`status`	No	Mine status (Active \| Abandoned \| Intermittent \| Temporarily Idled \| NonProducing), CSV.
`canvass`	No	Primary canvass (Coal \| M/NM \| Metal \| Nonmetal \| Sand & gravel \| Stone), CSV.
`mine_id`	No	MSHA mine id(s), CSV.
`operator`	No	Mine operator/company name — suffix/punctuation-insensitive.
`commodity`	No	Commodity/SIC or canvass fragment.
`entity_id`	No	Resolved operator entity UUID (pivots to business360).
`mine_name`	No	Mine name fragment.
`mine_type`	No	Surface \| Underground \| Facility (CSV).
`coal_metal`	No	C = coal, M = metal/non-metal.
`controller`	No	Controlling entity (parent) name fragment.
`operator_id`	No	MSHA operator id(s), CSV.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJul 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that it is a public-domain record search, includes a per-row price, and describes the scope (all coal and metal/non-metal mines under MSHA jurisdiction). It does not mention auth requirements or rate limits but sets appropriate expectations for a search tool.

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 description is 4 sentences, front-loaded with a question and immediate answer. It efficiently conveys the dataset, searchable fields, return fields, and pricing. No extraneous information; every sentence adds value.

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

Completeness4/5

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

Given the complexity (18 parameters, no output schema, no annotations), the description explains the dataset jurisdiction, what is returned (mine, operator, controller, commodity, employees, status), and pricing. It lacks output field details but covers the essential scope for a search tool.

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

Parameters3/5

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

The input schema has 100% coverage with descriptions for all 18 parameters. The description merely summarizes the parameter categories (e.g., 'by operator, mine name...') without adding new meaning beyond the schema. Thus it meets the baseline for high schema coverage.

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 clearly states it searches the MSHA Mines data set for mines and quarries, specifying the exact resource and actions. It includes context about the dataset (NAICS-21, OSHA-exempt) and lists returned fields, making the purpose unambiguous. The name and description distinguish it from siblings like msha_violations_search.

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 provides no explicit guidance on when to use this tool versus alternatives. It opens with a broad question but does not mention exclusions or conditions under which another tool would be more appropriate. There is no mention of sibling tools or when not to use this one.

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

All Govparse Government Data Gateway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct domain and specific action (e.g., FDA approvals vs clearances vs recalls; firmstanding business360 dossier vs search vs screen). Even overlapping concepts like 'business360' vs 'business360_lookup' are distinguished by input (UUID vs name+state). No two tools appear to do the same thing.

Naming Consistency5/5

All tools use a consistent lowercase snake_case pattern with domain prefix (e.g., fda_*, firmstanding_*, fmcsa_*, govcon_*). Action words (search, lookup, screen, feed, stats) follow predictable usage. The naming is uniform and easy to parse.

Tool Count4/5

38 tools is on the higher end but appropriate for a comprehensive government data gateway spanning multiple agencies and datasets. Each domain has a reasonable number of tools (e.g., FMCSA: 7, OFLC: 6). Could potentially be trimmed slightly, but overall well-scoped for the stated purpose.

Completeness5/5

The tool surface covers the major government data sources comprehensively: FDA (approvals, clearances, recalls), FMCSA (carrier census, safety, insurance, etc.), FSIS, DOJ/OFLC, OSHA/EPA/DOL enforcement, SEC insider filings, clinical trials, VA facilities/opportunities/vendors, and federal contracting. No obvious gaps for the stated gateway purpose.

Resources

Need Help?