Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

by biz.nibiashara
OverviewDiscussionsAdmin

Load vet pack — authority + BASICs + broker + OFAC name

vet_load
Read-only

Load vet pack — authority + BASICs + broker + OFAC name. One call before you tender: FMCSA authority and SMS BASICs for the carrier (USDOT or MC), FMCSA broker authority for the broker on the load (broker_mc), plus an OFAC name screen when you pass a legal name. Verdict is TENDER, HOLD or REJECT from those public fields only — no invented fraud score. Cites FMCSA QCMobile and OFAC as_of. $0.25 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcNocarrier MC/docket number (optional; give dot, mc or broker_mc)
dotNocarrier USDOT number (optional; give dot, mc or broker_mc)
nameNolegal name to OFAC-screen (optional)
broker_mcNobroker MC/docket number — runs the FMCSA broker-authority check (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / broker_mc
      Added value: +{
+  "description": "broker MC/docket number — runs the FMCSA broker-authority check (optional)",
+  "type": "string"
+}
    • changedInput schema / properties / dot / description
      Previous value: -"USDOT number (this or mc required)"New value: +"carrier USDOT number (optional; give dot, mc or broker_mc)"
    • changedInput schema / properties / mc / description
      Previous value: -"MC/docket number (this or dot required)"New value: +"carrier MC/docket number (optional; give dot, mc or broker_mc)"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint=false), it discloses the cost ($0.25 USDC on Base), that the tool call itself is free, the x402 payment handshake (402 → PAYMENT-SIGNATURE → delivery), the verdict scale (TENDER/HOLD/REJECT), the sourcing (FMCSA QCMobile, OFAC as_of), and the deliberate omission of any fraud score. This is substantial undisclosed-by-annotation context.

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?

Front-loaded with the pack's contents and scoped tightly, though the first line largely restates the title and a few clauses (cost, payment flow) sit as a run-on. Still, nearly every sentence carries load-bearing information.

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 must explain returns, and it does: the verdict values and the x402 URL to GET. Combined with the payment mechanics and sourcing, an agent has everything needed to call and interpret it.

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, but the description adds conditional meaning: broker_mc triggers the broker-authority check, name triggers the OFAC screen, and dot/mc cover the carrier. It clarifies behavior the schema only lists.

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 names a specific composite action and enumerates exactly what it bundles: FMCSA authority, SMS BASICs, FMCSA broker authority, and an OFAC name screen. This makes it distinguishable from the narrower siblings (check_carrier_authority, check_broker_authority, check_carrier_basics, screen_sanctions_name) despite not naming them, since it states it is the all-in-one pack.

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?

"One call before you tender" gives a clear triggering context, and the description attaches each check to its parameter. It does not explicitly say when to prefer the individual check_* tools over this bundle, so it stops short of full alternative routing.

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

All Ni Biashara Shelves — Africa FX, freight & compliance checks (x402) 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