Govparse Government Data Gateway

fmcsa_carrier_search

Which FMCSA-registered carriers match a name, state, entity type, fleet-size range, operating status, or authority status? Trigram name search over 4.4M+ census records — find a carrier's USDOT number, shortlist carriers in a lane state, or screen brokers vs carriers. Up to 100 rows per call, largest fleets first; total_matched caps at 1000 (total_matched_capped=true means narrow your filters). [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Carrier legal or DBA name fragment, case-insensitive (trigram match). Example: 'knight transportation'.
`sort`	No	field:direction — power_units \| total_drivers \| usdot. Example: 'power_units:desc'.
`limit`	No	Max rows to return (default 25, cap 100).
`state`	No	Physical-address state code(s), CSV. Example: 'TX,OK'.
`offset`	No	Rows to skip, for paging.
`entity_type`	No	carrier \| broker \| forwarder (CSV for multiple).
`power_units_max`	No	Maximum fleet size in power units.
`power_units_min`	No	Minimum fleet size in power units.
`authority_status`	No	Only carriers with an operating-authority record in this status: Active \| Pending \| Inactive \| Withdrawn.
`operating_status`	No	A (active) \| I (inactive) \| P (pending), CSV for multiple.

Schema Changelog

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

First observedJul 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It reveals trigram name search (case-insensitive), ordering by largest fleets first, a row cap of 100, total_matched cap of 1000, and pricing ($0.05/row). It also explains the meaning of total_matched_capped. This provides good behavioral insight, though auth and rate limits are not mentioned.

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?

The description is extremely concise: two sentences covering purpose, mechanism, use cases, limits, and pricing. Front-loaded with a question summarizing functionality, with no redundancy or unnecessary detail.

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 of 10 parameters and no output schema, the description covers the essential aspects: what the tool does, key filters, default ordering, limits, and cap behavior. It does not describe the output fields, but the mention of 'carrier's USDOT number' implies an output expectation. It is largely complete for an agent to use correctly.

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 and examples for all 10 parameters. The description adds some high-level context (e.g., trigram match for name, pricing per row related to limit) but does not significantly expand on individual parameter meanings. Baseline 3 is appropriate as schema already documents parameters well.

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 is a search tool for FMCSA-registered carriers, using trigram name search over 4.4M+ records, with multiple filter criteria and specific use cases. It effectively distinguishes from siblings like fmcsa_carrier_lookup (single carrier lookup) and fmcsa_carrier360 (comprehensive view), as those are not search tools.

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?

The description provides explicit use cases (find a carrier's USDOT number, shortlist carriers in a lane state, screen brokers vs carriers) and hints at when to narrow filters (when total_matched_capped is true). However, it does not directly compare to sibling tools, though the sibling names imply different purposes.

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?