Skip to main content
Glama

insurance_recommendation

Recommend cost-effective marine cargo insurance by comparing ICC clauses (A, B, C) with coverage, exclusions, and premium calculated from cargo value, loss profile, mode, and route risk.

Instructions

Recommend cost-effective MARINE CARGO INSURANCE for a shipment — the cover an importer needs but often under-buys. It prices the three Institute Cargo Clauses side by side: ICC (A) ALL-RISK (covers everything bar named exclusions — for valuable/fragile/theft-prone cargo), ICC (B) named-perils-broad (adds water-ingress but NOT theft), and ICC (C) MINIMUM (only major vessel casualties — no water, no theft) — showing what each COVERS and EXCLUDES. The premium = INSURED VALUE (CIF + 10% customary markup, the freight pulled server-side so the base is real) × the cargo's LOSS PROFILE (electronics/batteries load the rate; robust steel discounts it) × the MODE risk (air has a structurally lower loss rate than ocean — links to compare_modes) × the ROUTE risk (a Red-Sea/Cape-diverted lane spikes the separate WAR-RISK additional premium — links to the disruptions engine) × the deductible. It recommends the cost-effective cover level for your cargo and clarifies the Incoterms tie: CIF obliges the seller to buy only ICC (C) minimum, CIP obliges ICC (A) all-risk, and a FOB/CFR/CPT buyer gets NO seller insurance at all (must self-arrange). Modeled market-typical bands — NOT a broker's quote (regla 7). PREMIUM: pay per call with x402 (USDC on Base) or set a prepaid key (FREIGHT_PULSE_KEY). Same UN/LOCODE port normalization as get_spot_rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port (city, UN/LOCODE, or 'City, Country'). The route (incl. Red-Sea diversion) drives the war-risk premium.
dest_portYesDestination port (city, UN/LOCODE, or 'City, Country').
cargo_valueYesMerchandise value (USD) — REQUIRED. The insured value is CIF (cargo + freight) + 10%.
container_typeNoContainer size '20ft'/'40ft'/'40HC' (for the freight leg). Optional; defaults to '40ft'.
productNoProduct description to classify the cargo loss profile (e.g. 'bluetooth earbuds', 'steel coils'). Optional but improves the rate.
hs_codeNoExplicit HS code (alternative to product). Optional.
modeNoTransport mode for the loss profile: 'ocean' (default), 'air' (lower loss rate) or 'sea-air'. Optional.
deductible_fractionNoPolicy deductible as a fraction of insured value (0 = nil, 0.005 = 0.5% typical, 0.01, 0.02). A higher excess lowers the premium. Optional.
ship_dateNoIntended ship date (ISO). Optional; defaults to today.
markup_pctNoInsured-value markup over CIF (default 0.10 = the customary +10%). Optional.
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it is a recommendation tool using market-typical bands (not a broker's quote), details premium calculation components, payment per call or prepaid key, and UN/LOCODE normalization. No contradictions.

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 well-structured and front-loaded with the main purpose, then breaks down clauses, premium calculation, Incoterms, and payment. It is somewhat long but each sentence adds value; could be slightly more concise.

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?

Given the complexity (10 parameters, no output schema), the description is thorough, covering purpose, premium components, clauses, Incoterms, and payment. It lacks explicit output format but the premium computation details imply what is returned.

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 coverage is 100%, and the description adds extra context beyond schema descriptions, such as how origin port affects war-risk premium and how product classifies loss profile. This adds value without being redundant.

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 recommends cost-effective marine cargo insurance, specifying the verb 'Recommend' and the resource 'marine cargo insurance'. It distinguishes from siblings by detailing the comparison of Institute Cargo Clauses, which is unique among the listed tools.

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

Usage Guidelines4/5

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

The description provides clear context on when to use, including Incoterms implications (CIF, CIP, FOB/CFR/CPT) and payment model. It does not explicitly list alternatives among siblings, but the detailed Incoterms guidance helps decision-making.

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