Skip to main content
Glama

Where to find loads for a vehicle type

find_loads_for_vehicle
Read-onlyIdempotent

Return where freight comes from for a given vehicle type (box truck, cargo or sprinter van, hotshot pickup, dry van): load boards, Amazon Relay, final-mile and direct broker sources, plus the carrier-vetting requirements a carrier must clear before a broker releases a load.

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": {
      "vehicle": "<vehicle>"
    },
    "name": "find_loads_for_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicleYesVehicle type, e.g. 'box truck', 'cargo van', 'sprinter van', 'hotshot', 'dry van'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent lookup, so the description's main added value is clarifying what the response contains: freight sources plus carrier-vetting requirements. It does not mention rate limits or authentication, but it meaningfully supplements the safety profile with domain-specific return context.

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?

The definition is a single front-loaded sentence with no wasted words. It moves directly from the result ('where freight comes from') to the scope ('for a given vehicle type') to illustrative outputs.

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 no output schema, the description compensates well by naming the categories of information returned. It does not specify the response format (list, text, structured objects), but for a simple single-parameter lookup this is close to 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 100% and the single 'vehicle' parameter is already documented with examples in the schema. The description repeats the same vehicle examples and adds no syntax or formatting detail beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb ('Return where freight comes from') and resource ('for a given vehicle type'), then enumerates concrete outputs (load boards, Amazon Relay, final-mile and direct broker sources, carrier-vetting requirements). It clearly distinguishes this freight-source lookup from the ELD- and blog-oriented sibling tools.

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?

The context of use is implied (a carrier checking freight sources for a vehicle type), but there is no explicit 'use this when' guidance or mention of alternatives. Since no sibling tool directly overlaps, the implied usage is adequate but not fully articulated.

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