Skip to main content
Glama

LiveDataLink

by io.github.blackboxfoundry
OverviewDiscussionsAdmin

carrier_vetting_evidence_pack

Read-onlyIdempotent

Produce an auditable Carrier Vetting Pack for a freight broker. Resolve a US motor carrier by USDOT, MC, or legal name, then return the GO/CAUTION/NO-GO verdict, the exact FMCSA authority/insurance/safety evidence, sanctions/court/federal-award checks, source coverage and failures, retrieval timestamp, primary-source links, and a broker follow-up checklist. This is the evidence-first companion to carrier_vetting_score: use it when a human reviewer needs to save or forward the record. It is an analytical aid, not a substitute for direct FMCSA insurance and authority verification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcNoMC/MX number without the prefix.
dotNoUSDOT number (preferred exact identifier).
nameNoLegal carrier name when DOT/MC is unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / dot / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / mc / type
      Previous value: -"number"New value: +"integer"
  2. Changed4 schema fields changed
    • changedInput schema / properties / dot / description
      Previous value: -"USDOT number (preferred). Accepts 3405079 or USDOT 3405079."New value: +"USDOT number (preferred exact identifier)."
    • changedInput schema / properties / dot / type
      Previous value: -[
-  "number",
-  "string"
-]New value: +"number"
    • changedInput schema / properties / mc / description
      Previous value: -"MC/MX number. Accepts 123456 or MC-123456."New value: +"MC/MX number without the prefix."
    • changedInput schema / properties / mc / type
      Previous value: -[
-  "number",
-  "string"
-]New value: +"number"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine value beyond them: it discloses that source coverage and failures are surfaced, that a retrieval timestamp is included, and that the output is advisory rather than authoritative. It does not detail pagination or size limits, but for a read-only pack tool this is strong.

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?

Purpose and scope are front-loaded in the first sentence, with the alternative-tool routing at the end. The middle output enumeration is a dense comma-separated list, but each item is substantive and none is filler.

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?

With no output schema and no required parameters, the description carries the burden of explaining what comes back - and it does: verdict, evidence, sanctions/court/federal-award checks, source coverage and failures, timestamp, primary-source links, and a follow-up checklist. It also flags the authority limitation. Nothing material is missing for correct invocation.

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 description coverage is 100% and the schema already documents mc, dot and name, including that dot is the 'preferred exact identifier'. The description's 'Resolve a US motor carrier by USDOT, MC, or legal name' merely restates those fields, adding no format or precedence detail beyond what the schema provides.

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?

States a specific verb+resource ('Produce an auditable Carrier Vetting Pack for a freight broker'), names the resolution keys, and enumerates the concrete outputs (GO/CAUTION/NO-GO verdict, FMCSA evidence, sanctions checks). It explicitly differentiates itself from sibling carrier_vetting_score as the 'evidence-first companion'.

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?

Names the alternative (carrier_vetting_score) and the exact condition that selects this tool: 'use it when a human reviewer needs to save or forward the record.' It also states the exclusions - it is 'an analytical aid, not a substitute for direct FMCSA insurance and authority verification.'

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

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