Skip to main content
Glama

appointment_plan

Plan terminal appointment and box sequence to avoid demurrage and detention. Provides optimal pickup window, dual-transaction sequence, and expected D&D savings.

Instructions

Plan the terminal APPOINTMENT and the box sequence so you don't eat demurrage & detention. US/EU terminals require a timed appointment to pick up the import container and to return the empty; miss the window and dwell climbs and D&D starts. Give the lane + ship date and it reads the destination port congestion (iter7) at arrival, derives APPOINTMENT-SLOT availability (how far out the first slot is and how likely a desired slot is missed — the real dwell driver), then returns: the OPTIMAL PICKUP WINDOW (late enough not to pre-pay storage, with a reserve for a missed slot, by-date inside your free days), the PICKUP→EMPTY-RETURN sequence (a dual transaction where the port supports it to cut detention), and the expected D&D of the plan vs sending the trucker blind, with the saving. Proves: a congested port (LA/LB at peak) → tight slot window, book earlier, dual-transaction the empty → saves $X of D&D; a fluid port → same-day slots, relaxed window, no premium. Honest (regla 7): INDICATIVE — appointment availability, slot scarcity and dual-transaction behaviour are modeled by port & congestion band, NOT a live terminal appointment feed (eModal/Voyage/TideWorks). PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port (city name, UN/LOCODE, or 'City, Country').
dest_portYesDestination port — where the box is picked up & the empty returned.
container_typeNoContainer '20ft'/'40ft'/'40HC'. Optional; default '40ft'.
ship_dateNoShip date (YYYY-MM-DD) — sets the arrival window & congestion. Optional; default today.
discharge_clear_daysNoDays to discharge + customs-clear before the box is available for pickup. Optional; default 2.
import_free_daysNoYour contract's import (demurrage) free days. Optional — a regional default is used.
empty_return_free_daysNoYour contract's empty-return (detention) free days. Optional — a regional default is used.
Behavior5/5

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

No annotations exist, so the description fully covers behavioral traits. It honestly discloses that the tool uses a model, not live terminal feeds (eModal/Voyage/TideWorks), is indicative, and mentions premium pricing (pay per call with USDC). This level of transparency is exemplary.

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 description is detailed and well-structured, front-loading the core purpose and process. While every sentence adds value, it is somewhat lengthy (including examples and pricing). A slightly more concise version would earn a 5.

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 the complexity (7 parameters, no output schema), the description is complete: it explains inputs, the modeling approach, outputs (optimal pickup window, sequence, D&D savings), caveats, and pricing. No gaps remain for an agent to use the tool effectively.

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 each parameter is already described. The tool description adds overall context but does not significantly enhance parameter meanings beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool's purpose: planning terminal appointments and box sequence to avoid demurrage & detention. It explains the inputs and outputs in detail. However, it does not explicitly distinguish from sibling tools like dnd_strategy, which may overlap, so it misses the highest marks for differentiation.

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 description implies usage contexts (congested vs. fluid ports) and sets expectations that it is indicative, not a live feed. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., dnd_strategy) or when not to use it.

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/Baneado98/freight-pulse'

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