Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Pick the box that minimises billable weight

ecommerce-profitability_packaging-optimize
Read-onlyIdempotent

Try caller boxes and orientations with padding, compute dimensional and billable weight from a caller divisor, and pick the best by billable weight or box cost. Price $0.03 USDC. POST /api/v1/ecommerce-profitability/packaging-optimize. An unpaid call returns the x402 payment terms and does not run.

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": {
      "items": "<items>",
      "boxes": "<boxes>",
      "dimDivisor": "<dimDivisor>"
    },
    "name": "ecommerce-profitability_packaging-optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxesYesboxes, array. Required.
itemsYesitems, array. Required.
objectiveNoobjective, string, one of billable_weight, box_cost. Required.billable_weight
paddingCmNopaddingCm, number, from 0 to 100. Required.
dimDivisorYesdimDivisor, number. Required.

Output Schema

NameRequiredDescriptionDefault
bestNobest. Object.
sourcesNosources. Array.
rejectedNorejected. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is largely covered. The description nonetheless adds real behavioral facts: the $0.03 USDC price, the POST path, and that an unpaid call returns x402 payment terms without executing. It does not state how ties between equal-weight boxes are broken or whether padding is applied per side.

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 front-loaded sentences with no filler: the operation first, then price and endpoint, then the payment-gate caveat. Slight density cost from packing the divisor, padding and objective into one clause, but nothing is wasted.

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-value explanation is unnecessary, and the description covers purpose, cost, transport, and the payment precondition. For a stateless read-only compute endpoint with fully documented parameters, the remaining gaps (tie-breaking, orientation semantics) are minor.

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 100% schema description coverage the schema already documents all five parameters, so the baseline is 3. The description adds conceptual meaning by framing dimDivisor as the caller-supplied divisor driving dimensional weight and by pointing at padding and objective, but it does not explain orientation handling or the units/rounding of billable weight.

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 names a concrete operation: trying candidate boxes and orientations with padding, computing dimensional and billable weight from a divisor, and selecting the best by billable weight or box cost. That is a specific verb+resource statement an agent can act on, though differentiation from siblings is by domain vocabulary rather than an explicit contrast.

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 described optimization scenario (you have items and candidate boxes and want the cheapest billable-weight fit), but there is no explicit when-to-use, when-not-to-use, or named alternative among the pricing/unit-economics siblings. The x402 payment note tells the agent what happens on an unpaid call, which is helpful context but not usage routing.

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