Skip to main content
Glama

Argo Hub Fulfillment Ecommerce

Calculate a comparable monthly ecommerce logistics budget

calculate_logistics_costs
Read-only

Use to add a known monthly fulfillment fee, user-provided material and transport costs per physical parcel, and other monthly costs for one consistent ecommerce scenario. Unknown optional costs remain pending; no final total or per-order result is reported until all are supplied. Does not fetch carrier tariffs or accept a commercial quote.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monthlyFee": "<monthlyFee>",
      "parcels": "<parcels>",
      "commercialOrders": "<commercialOrders>"
    },
    "name": "calculate_logistics_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcelsYes
monthlyFeeYes
commercialOrdersYes
otherMonthlyCostsNo
materialsPerParcelNo
transportPerParcelNo

Output Schema

NameRequiredDescriptionDefault
pendingYes
completeYes
currencyYes
limitationsYes
vatIncludedYes
monthlyTotalYes
costPerParcelYes
knownSubtotalYes
costPerCommercialOrderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare read-only, closed-world, non-destructive behavior. The description adds meaningful behavior: optional costs remain pending and no final total or per-order result is reported until all are supplied. It also clarifies the external-data limitation, though consistency validation and rounding behavior are not covered.

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 three sentences, front-loaded with the use case, then the pending-cost rule, then exclusions. There is no filler, though the first sentence is dense and could be more cleanly structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only calculator with an output schema, the description covers the core operation, pending behavior, and exclusions. However, it omits the role of the required commercialOrders input and provides no sibling routing, which is a meaningful gap given 0% schema description coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain all six parameters. It explains monthlyFee, materialsPerParcel, transportPerParcel, otherMonthlyCosts, and implies parcels through 'per physical parcel,' but never explains the required commercialOrders input or clarifies units/currency. This leaves a required parameter semantically undefined.

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 states a specific calculation: adding a monthly fulfillment fee, per-parcel material and transport costs, and other monthly costs for one ecommerce scenario. It also rules out fetching carrier tariffs or accepting a commercial quote. The purpose is clear, though it does not directly differentiate from the sibling comparison and planning 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?

It begins with 'Use to...' and gives clear usage context, plus exclusions such as not fetching carrier tariffs and not accepting a commercial quote. It does not name alternatives like compare_warehouse_costs or estimate_fulfillment_plan, so sibling routing is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources