Skip to main content
Glama

Add carrier to watchlist

add_to_watchlist
Idempotent

Add a carrier to this account's watchlist (paid plans). Change alerts for the carrier's FMCSA record are delivered to the notification email and/or signed webhook (Pro+) configured for this monitor via alert_email and webhook_url. The carrier must have been looked up at least once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dot": "<dot>"
    },
    "name": "add_to_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
dotYesUSDOT number, 1-8 digits, e.g. "1234567"
alert_emailNo
webhook_urlNoHTTPS URL (Pro and Business)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true); the description adds genuinely new context: plan gating, prerequisite carrier lookup, and where alerts are delivered (notification email and/or signed webhook). It doesn't cover limits or what happens on a duplicate add beyond the idempotency hint.

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?

Three dense but purposeful sentences, front-loaded with the action and scope before prerequisites and parameter behavior. No filler, though the alert-delivery sentence is somewhat packed.

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?

For a 3-parameter, non-destructive write with no output schema, the description covers plan gating, prerequisites, and alert routing. It omits what the call returns and how already-watched carriers or quota limits are handled, which would be nice to have.

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?

The schema documents dot and webhook_url but leaves alert_email bare; the description fills that gap by explaining that alert_email and webhook_url configure the monitor's alert delivery channels, and adds a Pro+ tier constraint on webhook_url beyond 'HTTPS URL' in the schema. Useful meaning added on top of a 67% coverage 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?

Specific verb plus resource ('Add a carrier to this account's watchlist') with the plan scope stated up front. It is trivially distinguishable from siblings like remove_from_watchlist and list_watchlist without opening any schema.

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?

Gives two concrete preconditions — paid plan required and the carrier must have been looked up at least once — which implicitly routes the agent to lookup_carrier first. It does not explicitly name lookup_carrier or state what to do if the carrier is already watched, so it falls short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources