Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

vehicle_lookup

Read-onlyIdempotent

Look up road freight vehicle and trailer specs: internal dimensions, payload limits, pallet capacity, and features for 17 types including articulated, rigid, and van categories.

Instructions

Look up road freight vehicle and trailer specifications.

17 types covering articulated trailers (curtainsider, mega, box, reefer, double-deck, flatbed, low-loader, US 53ft/48ft), rigid trucks (7.5T to 26T), and vans (Luton, Transit, Sprinter). Returns internal dimensions, payload limits, pallet capacity, and features.

Use this tool when you need to:

  • Find vehicle specs by type (e.g., "standard-curtainsider")

  • Compare EU vs US trailer dimensions

  • Determine pallet capacity for vehicle selection

  • Check payload limits for heavy shipments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoVehicle slug (e.g., "standard-curtainsider"). Omit to list all.
categoryNoFilter by category
regionNoFilter by region

Implementation Reference

  • The 'vehicle_lookup' tool handler — defines the tool with name, description, schema, annotations, and a handler that calls apiGet('vehicles', ...) with optional slug, category, and region filters.
    const vehicleLookup: ToolDef = {
      name: 'vehicle_lookup',
      description: `Look up road freight vehicle and trailer specifications.
    
    17 types covering articulated trailers (curtainsider, mega, box, reefer, double-deck, flatbed, low-loader, US 53ft/48ft), rigid trucks (7.5T to 26T), and vans (Luton, Transit, Sprinter). Returns internal dimensions, payload limits, pallet capacity, and features.
    
    Use this tool when you need to:
    - Find vehicle specs by type (e.g., "standard-curtainsider")
    - Compare EU vs US trailer dimensions
    - Determine pallet capacity for vehicle selection
    - Check payload limits for heavy shipments`,
    
      schema: z.object({
        slug: z.string().optional().describe('Vehicle slug (e.g., "standard-curtainsider"). Omit to list all.'),
        category: z.enum(['articulated', 'rigid', 'van']).optional().describe('Filter by category'),
        region: z.enum(['EU', 'US']).optional().describe('Filter by region'),
      }).strict(),
    
      annotations: readOnlyAnnotations('Vehicle Lookup'),
    
      handler: async (args) =>
        apiGet('vehicles', { slug: args.slug, category: args.category, region: args.region }),
    };
  • Zod schema for vehicle_lookup — accepts optional slug (string), category (articulated|rigid|van), and region (EU|US). Uses .strict() to reject unknown keys.
    schema: z.object({
      slug: z.string().optional().describe('Vehicle slug (e.g., "standard-curtainsider"). Omit to list all.'),
      category: z.enum(['articulated', 'rigid', 'van']).optional().describe('Filter by category'),
      region: z.enum(['EU', 'US']).optional().describe('Filter by region'),
    }).strict(),
  • src/tools.ts:713-713 (registration)
    The ALL_TOOLS array that exports all ToolDefs, including vehicleLookup at index 17 (line 731).
    export const ALL_TOOLS: ToolDef[] = [
  • The apiGet helper function called by the vehicle_lookup handler — constructs a URL with query params and fetches JSON from the FreightUtils API.
    export async function apiGet(endpoint: string, params: Record<string, unknown>): Promise<unknown> {
      const url = new URL(`${BASE_URL}/${endpoint}`);
      for (const [k, v] of Object.entries(params)) {
        if (v === undefined || v === null || v === '') continue;
        url.searchParams.set(k, String(v));
      }
    
      const res = await fetch(url.toString(), {
        headers: { 'Accept': 'application/json' },
      });
    
      if (!res.ok) {
        const body = await res.text();
        throw new Error(`FreightUtils API error ${res.status}: ${body}`);
      }
    
      return res.json();
    }
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds that it returns internal dimensions, payload limits, and features, giving behavioral context beyond annotations.

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?

Description is a bit long but well-structured: purpose, type list, return info, and usage bullets. No redundant sentences.

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?

No output schema, but description clearly states what is returned. All parameters are documented, and annotations cover safety. Complete for a lookup tool.

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 has 100% coverage with descriptions for all three params. Description adds value by giving examples of slugs (curtainsider, mega, etc.) and explaining categories, which helps selection beyond enum values.

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?

Description clearly states tool looks up road freight vehicle and trailer specifications, lists 17 types, and specifies return values. It distinguishes itself from siblings like container_lookup or adr_lookup.

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

Usage Guidelines5/5

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

Explicit bullet list of when to use: find specs by type, compare EU/US dimensions, determine pallet capacity, check payload limits. Provides clear guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SoapyRED/freightutils-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server