Govparse Government Data Gateway

hrsa_hpsa_search

Where has the federal government designated a health-professional shortage? Search HRSA HPSAs by state, county, discipline (Primary Care | Dental Health | Mental Health), designation type, status, minimum HPSA score (0-26, higher = worse), population type, rural-only, or designated-since date. Returns the designation, score, geography, provider-to-population ratio, and shortage FTE — the buying moment for clinician-staffing, telehealth, and workforce vendors. [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	score \| designation_date \| shortage_fte :asc\|:desc. Default score:desc.
`limit`	No	Max rows (default 25, cap 100).
`rural`	No	true = rural / partially-rural only; false = non-rural.
`since`	No	Designated on or after this date (YYYY-MM-DD).
`state`	No	Primary state/territory code(s), CSV.
`county`	No	County name fragment.
`offset`	No	Rows to skip.
`status`	No	Designated \| Proposed for Withdrawal \| Withdrawn (CSV).
`hpsa_id`	No	Exact HPSA ID.
`min_score`	No	Minimum HPSA score (0-26, higher = worse).
`discipline`	No	Primary Care \| Dental Health \| Mental Health (CSV).
`population_type`	No	Population-type fragment (Low Income, Migrant Farmworker...).
`designation_type`	No	Designation type fragment.

Schema Changelog

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

AddedJul 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses pricing ($0.05/row), output fields, and that this is a search tool. Does not mention rate limits or auth, but reasonable for a public data source.

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?

Three concise sentences, front-loaded with purpose, lists key filters, and ends with value proposition. No wasted words.

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?

Describes output fields and pricing, which complements the 13-parameter schema. Lacks discussion of pagination handling beyond limit/offset, but sufficient for a search tool with no output schema.

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?

Schema coverage is 100%, so baseline is 3. Description adds marginal value by explaining the buying moment and output fields, but does not add new parameter-level semantics beyond what's in the schema.

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?

Clearly states the tool searches HRSA HPSAs with specific filters. Uses a question to frame the purpose and lists key parameters, distinguishing it from the sibling 'hrsa_mua_search' which focuses on medically underserved areas.

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 context for use (clinician-staffing, telehealth, workforce vendors) and lists output fields. Does not explicitly state when not to use or name alternatives, but the use case is clear.

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?