Skip to main content
Glama

Argo Hub Fulfillment Ecommerce

Compare avoidable warehouse expenses with outsourcing

compare_warehouse_costs
Read-only

Use when a merchant wants to compare genuinely avoidable monthly internal logistics expenses with the additional recurring expense of outsourcing the same operating scope. Include only changes: shared costs that remain equal are excluded from both sides. Optional transition costs determine a simple payback when monthly cash savings are positive. Founder time, speculative revenue and fixed costs that remain payable are not cash savings.

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": {
      "avoidableInternalMonthly": "<avoidableInternalMonthly>",
      "additionalOutsourcedMonthly": "<additionalOutsourcedMonthly>"
    },
    "name": "compare_warehouse_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
transitionCostNoOne-off switching costs, if known; absence is not zero.
avoidableInternalMonthlyYesMonthly internal cash expenses that would actually cease after outsourcing.
additionalOutsourcedMonthlyYesAdditional recurring cash expenses caused by outsourcing, excluding common unchanged costs.

Output Schema

NameRequiredDescriptionDefault
currencyYes
cashSavingYes
limitationsYes
vatIncludedYes
paybackMonthsYes
monthlyDifferenceYes
transitionCostPendingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, closed-world, non-destructive behavior, and the description adds substantive calculation rules: only changed costs are included, shared unchanged costs are excluded, payback is computed only when monthly savings are positive, and founder time/speculative revenue/fixed payable costs are not treated as savings. This goes beyond the annotations, though it does not discuss precision or error handling.

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?

Four sentences, each carrying a distinct rule or use condition, with the usage trigger front-loaded. It is dense but not padded; minor tightening could improve scannability.

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?

With an output schema and annotations carrying safety and return-shape information, the description supplies the remaining decision-critical context: inclusion/exclusion rules, payback condition, and common non-cash exclusions. It is complete enough for correct invocation, though it could note units or currency assumptions if those are not otherwise specified.

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 descriptions already cover all three parameters at 100%, so the baseline is 3. The description adds meaningful interpretation by clarifying that both monthly inputs should capture only changed costs and by explaining how the optional transition cost drives payback, which helps prevent misclassification.

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 uses a specific verb ('compare') and defines both sides of the comparison—avoidable internal monthly logistics expenses versus additional recurring outsourcing expense—within the same operating scope. It is operationally clear, but it does not explicitly name or contrast the sibling tools, so it falls short of the top score.

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 opens with a clear 'Use when' trigger describing the merchant's comparison scenario. It does not state when to prefer a sibling tool or when not to use this one, but the context is sufficient to select it for a cost-comparison task.

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