Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_cross_dock_throughput

Calculate daily pallet throughput, dock door utilization, and max capacity for cross-dock facilities from inbound trucks, pallets per truck, and turnaround time.

Instructions

Cross-Dock Logistics Throughput & Staging Transfer Time Calculator. Calculate daily pallet staging capacity, dock door utilization, and dwell turnaround time for inbound-to-outbound cross-docking distribution facilities. Discipline: LOGISTICS. Governing mathematical model / formula: Throughput = Inbound Pallets Transferred Directly to Outbound Doors (Target Dwell Time < 24 Hours).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of daily_pallet_throughput (Total Daily Pallet Throughput), dock_door_utilization_pct (Dock Door Utilization), max_potential_throughput (Theoretical Maximum Capacity), inventory_holding_reduction (Warehouse Storage Cost Saved) using daily_inbound_trucks (Daily Inbound Trucks in trucks/day), pallets_per_truck (Average Pallets Per Inbound Truck in pallets), dock_doors_count (Active Cross-Dock Doors in doors), turnaround_time_mins (Average Door Unload/Load Time (Mins) in minutes). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Cross-Dock Logistics Throughput & Staging Transfer Time Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "cross-dock-throughput"

    • category (string): "logistics"

    • name (string): "Cross-Dock Logistics Throughput & Staging Transfer Time Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.daily_pallet_throughput (Total Daily Pallet Throughput): Formatted display string (e.g. '576 Pallets / Day')

      • metrics.dock_door_utilization_pct (Dock Door Utilization): Formatted display string (e.g. '62.5% of Daily Capacity')

      • metrics.max_potential_throughput (Theoretical Maximum Capacity): Formatted display string (e.g. '921 Pallets / Day')

      • metrics.inventory_holding_reduction (Warehouse Storage Cost Saved): Formatted display string (e.g. '100% Elimination of Put-Away')

    • execution_time_ms (number): Latency in milliseconds.

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": "omni_cross_dock_throughput"
  }
}

Input Schema

NameRequiredDescriptionDefault
dock_doors_countNoActive Cross-Dock Doors (doors). Total available loading dock bays. Default: 18. Min: 4. Max: 150.
pallets_per_truckNoAverage Pallets Per Inbound Truck (pallets). Standard trailer pallet load. Default: 24. Min: 10. Max: 30.
daily_inbound_trucksNoDaily Inbound Trucks (trucks/day). Trailers arriving at inbound unloading doors. Default: 24. Min: 2. Max: 250.
turnaround_time_minsNoAverage Door Unload/Load Time (Mins) (minutes). Forklift turnaround time per trailer. Default: 45. Min: 15. Max: 180.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it declares the tool read-only, idempotent, stateless with zero side effects, deterministic, and specifies that out-of-bounds inputs return a safe diagnostic error status rather than throwing. It falls short of explaining how each metric is actually derived (e.g. how dock_door_utilization_pct is normalized against max_potential_throughput), so the computation itself remains a black box.

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?

The definition is sectioned with clear headers and front-loads purpose before parameters and returns, so an agent can stop reading early. It is somewhat verbose — the marketing line about 'eliminating LLM arithmetic mistakes and formula hallucinations' and the repeated calculator name in the RETURNS block are padding — but most length is justified by the absent output schema.

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?

There is no output schema, so the detailed RETURNS block enumerating status, calculator, category, formula, inputs echo, the four formatted metric strings, and execution_time_ms is genuinely necessary and complete. Combined with bounds/validation behavior and the domain model, an agent has everything needed to call it and interpret the result.

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%, so the input schema already documents all four parameters with units, defaults, and min/max bounds; the description mostly restates those names and units. It does add value by mapping inputs to the specific metrics they feed and labeling each output's business meaning, but it contributes no new parameter semantics such as interaction effects or edge-case behavior.

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 opens with a specific noun phrase ('Cross-Dock Logistics Throughput & Staging Transfer Time Calculator') and spells out the concrete outputs (daily pallet throughput, dock door utilization, dwell turnaround) and domain (inbound-to-outbound cross-docking). It also names the sibling it is not (omni_universal_query), so an agent can distinguish it without opening the schema.

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?

It provides an explicit WHEN TO USE block listing the four computed outputs and the six-and-four input parameters they derive from, a WHEN NOT TO USE exclusion for qualitative/unquantified work, and an explicit SIBLING ROUTING rule pointing dynamic multi-discipline dispatch to omni_universal_query. When-to-use, when-not-to-use, and the alternative are all named.

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

Deploy Server

Other Tools