Skip to main content
Glama

Argo Hub Fulfillment Ecommerce

Estimate an Argo Hub fulfillment plan in Spain

estimate_fulfillment_plan
Read-only

Use when a merchant wants to check which public Argo Hub plan fits an ecommerce operation in Spain. Checks equivalent orders (one per prepared parcel), active SKU, PEA storage, inbound receipts and pallets together. Not for parcel tracking, live stock, competitor rankings, carrier quotes or automatic booking. Product suitability, per-arrival size and integration require review.

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": {
      "equivalentOrders": "<equivalentOrders>",
      "activeSku": "<activeSku>",
      "storagePea": "<storagePea>",
      "inboundReceipts": "<inboundReceipts>",
      "inboundPallets": "<inboundPallets>"
    },
    "name": "estimate_fulfillment_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoes
activeSkuYes
storagePeaYesSimultaneously occupied reference storage positions. Fractions require actual consolidation and released space.
inboundPalletsYesPallets received over the month; not stored stock. Use 0 for parcels-only receipts.
inboundReceiptsYes
equivalentOrdersYesPrepared physical parcels per month; a two-parcel commercial order counts as two. Not a hypothetical peak allowance.
largestArrivalPalletsNoPallets in the largest single inbound arrival, when known. An arrival over two pallets requires a specific review.

Output Schema

NameRequiredDescriptionDefault
reasonYes
statusYes
sourcesYes
currencyYes
planNameYes
conditionsYes
monthlyFeeYes
vatIncludedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a safe, closed-world read (readOnlyHint true, openWorldHint false, destructiveHint false), so the description only needs to add context, and it does: the result is a combined estimate across several dimensions at once, not a live quote or a booking. It also discloses the estimate's limits (product suitability, per-arrival size and integration are out of scope and need review), which is useful non-obvious behavior.

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?

Three tight sentences with the primary trigger front-loaded and the exclusions packed into one compact list. Nothing is redundant, though the final sentence about review is slightly clipped and could be clearer about which parameter triggers it.

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?

An output schema exists, so return values need no explanation, and the annotations carry the safety profile. Combined with the scope and exclusion statements, the definition covers what an agent needs to decide whether to call it. It falls short of 5 only because the parameter-level guidance is thin relative to seven inputs and five required fields.

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?

With 57% schema coverage and 7 parameters, the description partly compensates by glossing the core inputs, notably 'equivalent orders (one per prepared parcel)' and the joint treatment of storage, receipts and pallets. However, it says nothing about language, storagePea granularity, or largestArrivalPallets beyond noting that per-arrival size needs review. The remaining meaning is left to the schema, so a baseline-plus score 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 gives a specific verb-plus-resource: check which public Argo Hub plan fits an ecommerce operation in Spain, and enumerates the inputs considered (equivalent orders, active SKU, PEA storage, inbound receipts, pallets). It is clearly distinguishable from a cost calculator because it frames the output as plan fit. It does not explicitly name the sibling tools it should be preferred over, so it stops short of a 5.

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?

Usage is stated up front ('Use when a merchant wants to check...') and the negative space is unusually well covered: not for parcel tracking, live stock, competitor rankings, carrier quotes or automatic booking. It also flags that product suitability, per-arrival size and integration require review. The only gap is that it does not route the agent to a specific alternative tool for the excluded cases.

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