Skip to main content
Glama
Sign In

Fmcsa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fmcsa Carrier Lookup

fmcsa_carrier_lookup
Read-onlyIdempotent

Look up a US motor carrier (trucking/bus company) in the FMCSA census by USDOT number, MC/docket number, or company name. Keyless. Returns legal & DBA name, physical address, active/inactive status, interstate/intrastate operation, hazmat flag, fleet size (power units, trucks), driver counts, and cargo types carried. Pass dot_number (or mc_number, or name) directly, or the generic by + value pair. For carrier authority (broker status) use fmcsa_operating_authority; for safety scores use fmcsa_safety_snapshot.

Input Schema

NameRequiredDescriptionDefault
byNoAlternative calling shape: "dot" = USDOT number, "mc" = MC/docket number, "name" = company name; value goes in `value`.
nameNoCarrier company name to look up, e.g. "swift transportation".
valueNoThe lookup value when using `by`: a USDOT number (e.g. "54283"), MC/docket number (e.g. "136818"), or carrier name.
mc_numberNoMC/docket number to look up, e.g. "136818" or "MC136818".
dot_numberNoUSDOT number to look up, e.g. 54283. The simplest way to call this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "by": "dot",
-    "value": "54283"
-  },
-  {
-    "by": "name",
-    "value": "swift transportation"
-  }
-]New value: +[
+  {
+    "dot_number": "54283"
+  },
+  {
+    "by": "name",
+    "value": "swift transportation"
+  }
+]
    • changedInput schema / properties / by / description
      Previous value: -"\"dot\" = USDOT number, \"mc\" = MC/docket number, \"name\" = company name."New value: +"Alternative calling shape: \"dot\" = USDOT number, \"mc\" = MC/docket number, \"name\" = company name; value goes in `value`."
    • addedInput schema / properties / dot_number
      Added value: +{
+  "description": "USDOT number to look up, e.g. 54283. The simplest way to call this tool.",
+  "type": [
+    "number",
+    "string"
+  ]
+}
    • addedInput schema / properties / mc_number
      Added value: +{
+  "description": "MC/docket number to look up, e.g. \"136818\" or \"MC136818\".",
+  "type": [
+    "number",
+    "string"
+  ]
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Carrier company name to look up, e.g. \"swift transportation\".",
+  "type": "string"
+}
    • changedInput schema / properties / value / description
      Previous value: -"The lookup value: a USDOT number (e.g. \"54283\"), MC/docket number (e.g. \"136818\"), or carrier name (e.g. \"swift transportation\")."New value: +"The lookup value when using `by`: a USDOT number (e.g. \"54283\"), MC/docket number (e.g. \"136818\"), or carrier name."
    • changedInput schema / required
      Previous value: -[
-  "by",
-  "value"
-]New value: +[]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "by": "dot",
+    "value": "54283"
+  },
+  {
+    "by": "name",
+    "value": "swift transportation"
+  }
+]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds value by noting 'Keyless' (no authentication required) and enumerating the specific data fields returned, giving the agent a clear picture of what to expect.

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 the core purpose. Each sentence earns its place: purpose, return values, calling conventions and alternatives. No redundant wording.

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 moderate complexity and absence of an output schema, the description covers the main return fields and calling options. It does not mention edge cases like not-found behavior or error handling, which would have made it fully complete, but it is still highly informative.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by explaining the relationship between the direct parameters (dot_number, mc_number, name) and the generic by/value pair, clarifying that they are alternative calling shapes. This goes beyond the schema's individual property descriptions.

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 the tool looks up a US motor carrier by USDOT number, MC/docket number, or company name, and lists concrete return fields. It distinguishes itself from sibling tools by explicitly naming the alternatives for related functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use this tool (carrier census lookup) versus alternatives ('For carrier authority... use fmcsa_operating_authority; for safety scores use fmcsa_safety_snapshot'). It also clarifies the different calling conventions (direct params vs by/value pair).

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