Skip to main content
Glama
Sign In

Fmcsa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fmcsa Search Carriers

fmcsa_search_carriers
Read-onlyIdempotent

Search US motor carriers by company name (partial, case-insensitive) in the FMCSA census, ranked by fleet size. Keyless. Returns USDOT number, legal/DBA name, city/state, power units, drivers, and status. Optionally filter by 2-letter state. Use fmcsa_carrier_lookup for full detail on a returned USDOT number.

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name or fragment, e.g. "swift transport".
limitNoMax results (1-50, default 15).
stateNoOptional 2-letter physical state filter, e.g. "TX".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "swift transport"
+  },
+  {
+    "limit": 10,
+    "name": "schneider",
+    "state": "TX"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds 'Keyless' (no API key required) and 'ranked by fleet size', offering useful behavioral context beyond annotations. No contradictions.

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?

Two sentences plus a clear alternative usage sentence. No redundant or irrelevant information. Efficient and front-loaded.

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?

Despite no output schema, description clearly enumerates return fields (USDOT number, legal/DBA name, city/state, power units, drivers, status). Specifies optional state filter and ranking by fleet size. Fully addresses the tool's complexity and context.

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 that name is case-insensitive, which is not in the schema's parameter description. Other parameters are adequately described in schema. Minor added value, so score remains 3.

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 US motor carriers by company name (partial, case-insensitive), returns specific fields, and ranks by fleet size. Distinguishes from sibling fmcsa_carrier_lookup.

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?

Explicitly directs to use fmcsa_carrier_lookup for full details on a returned USDOT number, providing clear alternative. Does not fully enumerate when not to use this tool, but coverage is strong.

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

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