Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Compare bundle margin with separate sales

ecommerce-profitability_bundle-pricing
Read-onlyIdempotent

Compute separate and bundle margins, discount depth, margin delta and the break-even bundle price from caller component and bundle fees. Price $0.02 USDC. POST /api/v1/ecommerce-profitability/bundle-pricing. 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": {
      "components": "<components>",
      "bundle": "<bundle>"
    },
    "name": "ecommerce-profitability_bundle-pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleYesbundle, object. Required.
componentsYescomponents, array. Required.

Output Schema

NameRequiredDescriptionDefault
bundleNobundle. Object.
sourcesNosources. Array.
separateNoseparate. Object.
limitationsNolimitations. Array.
marginDeltaNomarginDelta. Number.
discountDepthNodiscountDepth. Number.
breakEvenBundlePriceNobreakEvenBundlePrice. Number.

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 readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.02 USDC charge, the POST transport path, and the crucial fact that an unpaid call returns x402 payment terms instead of results. Missing only note on response shape, which the output schema covers.

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 short sentences, front-loaded with the computation and followed by cost and payment-failure behavior. The endpoint path is arguably overhead for an agent, but nothing is padded or repeated.

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 present, the description needn't explain return values, and it does cover cost and the unpaid-call path. The remaining gap is monetary units (integer minor units vs. whole currency) and how component quantities map to bundle price, which matters for correct invocation of a pricing 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 coverage is 100% and nested fields carry their own descriptions, so the baseline applies. The phrase 'caller component and bundle fees' confirms the two top-level inputs but adds no meaning about units, currency, or whether prices are per-unit versus totals — the most consequential ambiguity for a margin calculation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific computation and enumerates its outputs: separate and bundle margins, discount depth, margin delta, and break-even bundle price, computed from caller-supplied component and bundle fees. That is concrete enough to separate it from sibling analytics tools such as unit-economics or price-elasticity-estimate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what it computes but never says when to choose it over alternatives like ecommerce-profitability_unit-economics, nor when it is inappropriate (e.g. single-SKU comparisons). The only conditional stated is the payment gate, which is not usage guidance for the analytical 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