UNITECARGO U.S. Logistics Provider Directory

Search UNITECARGO providers

search_providers

Read-onlyIdempotent

Search active, verified U.S. logistics provider profiles using bounded directory filters. Returns canonical UNITECARGO profile links and evidence freshness, without contact fields or write actions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_providers"
  }
}

Input Schema

Name	Required	Description
`city`	No	Exact city name, matched case-insensitively.
`name`	No	Partial company name.
`page`	No	One-indexed results page.
`limit`	No	Maximum providers per page.
`state`	No	Two-letter U.S. state or district code.
`service`	No	Exact primary service category.
`specialty`	No	Exact documented specialty.
`cargo_type`	No	Required documented cargo specialization.
`certification`	No	Exact documented certification.
`equipment_type`	No	Required documented equipment type.
`transport_mode`	No	Required documented transport mode.

Output Schema

Name	Required	Description
`providers`	Yes	Matching active, verified provider summaries.
`pagination`	Yes	Page, limit, totals, and navigation flags.
`applied_filters`	Yes	Normalized filters applied to the query.
`evidence_policy`	Yes	Freshness threshold and verification caveat.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the return shape (canonical profile links plus evidence freshness) and a meaningful limitation (no contact fields), which prevents the agent from over-expecting results.

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?

Two sentences, zero filler, and the scope constraint is front-loaded before the return/limitation clause. Every clause carries distinct information.

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?

With an output schema present the description needn't explain return structure, yet it still characterizes it; with 11 fully documented parameters and complete annotations, the remaining need is only routing information. That gap keeps it just short of 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 description coverage is 100% with 4 enums fully enumerated, so the schema carries all parameter meaning including matching semantics ('exact', 'partial', 'required documented'). The description adds only the generic phrase 'bounded directory filters' and no per-parameter nuance, which is the baseline expectation when the schema is complete.

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

Purpose4/5

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

The description states a specific verb (search) and resource (active, verified U.S. logistics provider profiles), plus the scoping constraints that define the result set. It implicitly separates itself from get_provider (single-record fetch) by being a filtered directory search, but it never names the sibling to make the distinction explicit.

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

Usage Guidelines3/5

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

'using bounded directory filters' implies the intended use, and 'without contact fields or write actions' signals what the tool is not for. However, there is no explicit routing guidance telling the agent when to fall back to get_provider for a full profile or get_directory_stats for aggregate counts.

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

All UNITECARGO U.S. Logistics Provider Directory tools Inspect

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

Need Help?