Skip to main content
Glama

4fillment

Estimate monthly cost

estimate_monthly_cost
Read-onlyIdempotent

Line-by-line monthly fee estimate from order volume, weight, storage and extras, with the monthly minimum applied. Non-standard packaging returns custom_quote_required.

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": {
      "monthly_orders": "<monthly_orders>",
      "avg_order_weight_lb": "<avg_order_weight_lb>"
    },
    "name": "estimate_monthly_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagingNoHow orders are packed. kitting, multi_step, fragile_special_handling and other need a custom quote.
sku_countNoNumber of distinct SKUs.
bins_storedNoBins in storage at month end (for stock smaller than a pallet).
monthly_ordersYesOrders shipped per month.
pallets_storedNoStandard pallets (up to 48 in tall) in storage at month end.
shelves_storedNoShelves in storage at month end.
items_per_orderNoAverage units per order (default 1).
include_ai_accessNoInclude the AI Access add-on (operate the account from an AI assistant). Ignored while the add-on is not offered.
inserts_per_orderNoSimple inserts (a flyer or a card) per order.
returns_per_monthNoReturned units processed per month.
avg_order_weight_lbYesAverage shipped weight per order, in pounds.
tall_pallets_storedNoTall pallets (up to 70 in) in storage at month end.
lot_or_expiry_trackedNoWhether products need lot or expiry tracking.
packaging_supplied_byNoWho supplies boxes and mailers.
product_labels_per_monthNoProduct labels (e.g. FNSKU) applied per month.
inbound_cartons_per_monthNoLoose cartons received per month.
inbound_pallets_per_monthNoPallets received per month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavior beyond annotations by stating that the estimate applies the monthly minimum and that non-standard packaging returns custom_quote_required. It still does not describe the full returned estimate structure, which matters because there is no output schema.

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 two tight sentences with the main purpose front-loaded. Every sentence adds value, and there is no redundant or filler wording.

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 rich annotations and complete input-schema descriptions, the definition is largely complete: it says what is estimated and how the custom-quote edge case behaves. Because there is no output schema, the description could say more about the returned line items, totals, or assumptions, but it is sufficient for correctly invoking the 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 description coverage is 100%, so the schema already documents all 17 parameters, including the packaging enum and its custom-quote condition. The description broadly groups inputs into order volume, weight, storage, and extras, but it adds little parameter-level meaning beyond what the schema provides.

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 verb and resource: 'Line-by-line monthly fee estimate from order volume, weight, storage and extras.' It makes the tool's scope clear, but it does not explicitly distinguish itself from siblings such as get_rate_card or get_service_overview.

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?

Usage is implied by the description of inputs and the monthly minimum, and there is a conditional note that non-standard packaging returns custom_quote_required. However, it does not say when to use this tool versus alternatives like get_rate_card, nor does it state prerequisites or exclusions.

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