Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

uld_lookup

Read-onlyIdempotent

Look up air freight ULD specifications including dimensions, weights, usable volume, compatible aircraft, and deck position by IATA code, category, or deck filter.

Instructions

Look up air freight ULD (Unit Load Device) specifications.

15 types including AKE (LD3), PMC main deck pallet, temperature-controlled containers, and more. Returns dimensions, weights, usable volume, compatible aircraft, and deck position.

Use this tool when you need to:

  • Find ULD specs by IATA code (e.g., "AKE", "PMC")

  • Compare container vs pallet ULD types

  • Check which ULDs fit on lower deck vs main deck

  • Find aircraft-compatible ULDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoULD code (e.g., "AKE", "PMC"). Omit to list all.
categoryNoFilter by category
deckNoFilter by deck position

Implementation Reference

  • The handler function for uld_lookup. It calls apiGet with endpoint 'uld' and passes optional query parameters: type, category, deck.
      handler: async (args) =>
        apiGet('uld', { type: args.type, category: args.category, deck: args.deck }),
    };
Behavior4/5

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

Annotations already declare the tool as read-only, non-destructive, and idempotent, so the safety profile is fully covered. The description adds value by detailing the return fields (dimensions, weights, volume, aircraft, deck), giving the agent a clear expectation of 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?

The description is concise at approximately 80 words, front-loads the action, and uses bullet points for usage guidelines. Every sentence adds value without redundancy.

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?

Given no output schema, the description adequately describes return values (dimensions, weights, volume, aircraft, deck). It also mentions 15 types and provides parameter usage notes. No gaps remain for a lookup tool.

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% with descriptions and enums for each parameter. The description adds examples (e.g., 'AKE', 'PMC') and restates filtering options, which is helpful but does not significantly exceed schema information. 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 clearly states the tool looks up air freight ULD specifications, including specific details like dimensions, weights, volume, aircraft compatibility, and deck position. It distinguishes itself from siblings like container_lookup by focusing on ULDs, a specific air freight container/pallet type.

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?

The description provides explicit use case scenarios in a bulleted list, such as finding specs by IATA code, comparing types, checking deck fit, and finding aircraft-compatible ULDs. This offers clear guidance on when to use the tool versus alternatives.

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