Skip to main content
Glama
Sign In

LiveDataLink

by io.github.blackboxfoundry
OverviewDiscussionsAdmin

carrier_monitor_recheck

Read-onlyIdempotent

Recheck an existing carrier snapshot and identify meaningful changes since the previous check. Accepts a DOT/MC/name plus the prior result or snapshot as previous_snapshot, then compares authority, identity, insurance summary, BASIC alerts, crashes, out-of-service indicators, safety rating, and verdict. Returns unchanged/changed status, a severity, field-level changes, and the next reviewer action. Store the returned current_snapshot in your own system and call this on a schedule; LiveDataLink does not silently retain customer watchlists.

Input Schema

NameRequiredDescriptionDefault
mcNoMC/MX number without the prefix.
dotNoUSDOT number (preferred).
nameNoCarrier legal name when DOT/MC is unavailable.
formatNoReport format. Defaults to markdown.
previous_snapshotYesPrior carrier_vetting result or JSON snapshot returned by an earlier call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / previous_snapshot / anyOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]
    • addedInput schema / required
      Added value: +[
+  "previous_snapshot"
+]
  2. 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"
  3. Changed5 schema fields changed
    • changedInput schema / properties / dot / description
      Previous value: -"USDOT number (preferred). Accepts 3405079 or USDOT 3405079."New value: +"USDOT number (preferred)."
    • 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"
    • removedInput schema / properties / previous_snapshot / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  }
-]
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/no-destructive, and the description adds context beyond them: results are classified unchanged vs changed with a severity, and critically that LiveDataLink does not silently retain watchlists, so state lives with the caller. It also describes the return payload categories, which matters since no output schema exists.

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 tight sentences: what it does, what it accepts and compares, what it returns, and the state-ownership caveat. No filler, and the core purpose is 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?

With no output schema, the description carries the return-value burden and does so (unchanged/changed status, severity, field-level changes, next reviewer action). It also covers the required-input workflow and the statelessness constraint, leaving nothing an agent needs in order to invoke it 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?

Schema coverage is 100%, with per-field descriptions for mc, dot, name, format, and previous_snapshot, so the baseline is 3. The description restates the identifier inputs and the previous_snapshot role without adding format or validation detail beyond 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?

States a specific verb (recheck) and resource (carrier snapshot) and defines the operation as a diff against a prior snapshot rather than a fresh lookup. The list of compared domains (authority, identity, insurance, BASIC alerts, crashes, OOS, safety rating, verdict) makes it unmistakably distinct from the sibling vetting/lookup 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?

Makes the prerequisite explicit (requires a prior result passed as previous_snapshot) and prescribes the operational pattern: store current_snapshot and call on a schedule. It does not name a specific alternative sibling (e.g. carrier_vetting_score or fmcsa_safety_scores) for a first-time/no-snapshot case, so the exclusion set is only implied.

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