Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Estimate own-price elasticity from history

ecommerce-profitability_price-elasticity-estimate
Read-onlyIdempotent

OLS of ln(units) on ln(price) with optional week or month seasonal dummies, classical standard errors and a 95% t interval from caller price/quantity history. Price $0.04 USDC. POST /api/v1/ecommerce-profitability/price-elasticity-estimate. 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": {
      "observations": "<observations>"
    },
    "name": "ecommerce-profitability_price-elasticity-estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonalityNoseasonality, string, one of none, week_of_year, month. Required.none
observationsYesobservations, array. Required.
promoFlagFieldNopromoFlagField, value. Optional.

Output Schema

NameRequiredDescriptionDefault
nNon. Number.
r2Nor2. Number.
ci95Noci95. Array.
sourcesNosources. Array.
stdErrorNostdError. Number.
warningsNowarnings. Array.
elasticityNoelasticity. Number.
limitationsNolimitations. Array.
droppedZeroUnitsNodroppedZeroUnits. Number.
priceVariationCvNopriceVariationCv. Number.

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 declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the charge is $0.04 USDC, the endpoint is POST /api/v1/ecommerce-profitability/price-elasticity-estimate, and a call without payment returns the x402 payment terms instead of running. It stops short of stating any minimum sample size or failure modes for a regression with too few observations, which keeps it at 4.

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?

Three short sentences, densely packed and front-loaded: method and output first, then cost and endpoint, then the payment-failure behavior. Every clause carries information an agent would otherwise have to guess, and there is no filler.

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 description covers method, cost, endpoint and payment semantics for a moderately complex statistical tool. The main remaining gap for correct invocation is data sufficiency — no guidance on minimum observations or what happens with degenerate/degenerate price variation.

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 baseline is 3, and the schema already names all three parameters with types and constraints. The description adds statistical meaning to 'seasonality' by explaining these are optional week or month seasonal dummies, which goes somewhat beyond the enum documentation. It says nothing about promoFlagField or the per-observation promo field, so the added value is partial.

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 precise verb and method: an OLS regression of ln(units) on ln(price) with optional seasonal dummies, classical standard errors and a 95% t interval. This is far more specific than the title and immediately identifies the output an agent will get. It does not, however, position the tool against any named sibling (e.g. unit-economics or competitive-price-index), so it stays at 4.

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?

The phrase 'from caller price/quantity history' implies the required input context, but there is no explicit statement of when to choose this tool versus the other pricing tools, nor any preconditions such as minimum observation count or data-quality requirements. The only explicit routing rule is about payment ('an unpaid call returns the x402 payment terms and does not run'), which is conditional behavior rather than use-case guidance.

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