Skip to main content
Glama

freight-intel

by com.dropwatchhq
OverviewDiscussionsAdmin

switch_signal

The real-time factor-SWITCH lead feed — the edge RigDig's static annual UCC buckets cannot show. PRIMARY = VIRGIN: a fresh authority with NO factor UCC-1 lien on record yet — the populated everyday flow, first factor to call wins (no factor yet — live). SECONDARY = TERMINATED: a UCC-3 termination just hit the carrier's factor lien (carrier now factor-free — highest-value lead). UCC-3 terminations are genuinely RARE — surfaced when they occur; an empty terminated list is honest, not a dead feed. Omit type to get the default (leads with primary=virgin, carries secondary=terminated). UCC coverage is partial and marked HONESTLY per state (uccCoverage); a carrier in a non-covered state is never labelled 'virgin'. Filter by type and state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNovirgin (populated primary) | terminated (rare secondary). Omit for both — leads with virgin.
limitNo
stateNo2-letter state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / description
      Previous value: -"virgin | terminated. Omit for both."New value: +"virgin (populated primary) | terminated (rare secondary). Omit for both — leads with virgin."
  2. Added

TDQS

C2.9/5.0
Behavior4/5

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

Since annotations are absent, the description carries the full burden and discloses key behaviors: partial UCC coverage marked honestly, empty terminated list is truthful, default type behavior, and the rarity of UCC-3 terminations. This adds significant context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, dense with domain jargon, and lacks clear structure. It uses stream-of-consciousness style (e.g., 'PRIMARY = VIRGIN: a fresh authority...') rather than concise, front-loaded sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers type, state, default behavior, and data honesty, but does not explain the output format (no output schema) or the role of the 'limit' parameter. For a tool with 3 params and no annotations, this is adequate but not complete.

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 67% (type and state described). The description explains the meaning of 'virgin' and 'terminated' and the default when type is omitted, adding value beyond schema. However, the 'limit' parameter is not mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool is a 'real-time factor-SWITCH lead feed' but does not use a clear verb like 'list' or 'get'. The purpose is implied but obscured by jargon, making it less accessible for an AI agent.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus sibling tools (e.g., new_authority_feed, search_carriers). The description contrasts with 'static annual UCC buckets' but does not mention alternatives or exclusion criteria.

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

All freight-intel 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