Skip to main content
Glama

BRAINIAC Ecommerce Seller Profitability

Price index and rank vs competitors

ecommerce-profitability_competitive-price-index
Read-onlyIdempotent

Compare our landed price (price + shipping) with in-stock competitor landed prices to return median index, min and rank. Price $0.02 USDC. POST /api/v1/ecommerce-profitability/competitive-price-index. 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": {
      "ourPrice": "<ourPrice>",
      "competitors": "<competitors>"
    },
    "name": "ecommerce-profitability_competitive-price-index"
  }
}

Input Schema

NameRequiredDescriptionDefault
ourPriceYesourPrice, integer, from 0 to 9007199254740991. Required.
competitorsYescompetitors, array. Required.
ourShippingNoourShipping, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
ofNoof. Number.
rankNorank. Number.
indexNoindex. Number.
sourcesNosources. Array.
ourLandedNoourLanded. Number.
limitationsNolimitations. Array.
competitorMinNocompetitorMin. Number.
competitorMedianNocompetitorMedian. Number.
excludedOutOfStockNoexcludedOutOfStock. Number.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely non-obvious behavior: a $0.02 USDC charge via x402, and that an unpaid call returns payment terms rather than executing. It omits whether results are cached or how stale competitor data may be, but the payment disclosure is the critical risk an agent needs.

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 with the core comparison and return values front-loaded, followed by cost and the degradation path for unpaid calls. The endpoint path is the only arguably removable element, and it is one clause.

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 not be explained, and annotations carry the read-only/idempotent profile; the description covers the payment gate that no structured field expresses. The remaining gap is the unit basis of the integer price fields, which matters for a money-comparison tool.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: that price inputs are 'landed' (price + shipping), which explains why ourShipping and competitor shipping exist and how they are combined. It also clarifies that only in-stock competitors enter the index, giving semantic weight to the inStock flag. Units for the integer price fields remain unstated.

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 specific operation: comparing 'our landed price (price + shipping)' against 'in-stock competitor landed prices' and returning 'median index, min and rank'. That is a concrete verb-plus-resource statement an agent can match to a request. It does not name or rule out any sibling tool, so differentiation is left to the reader.

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 scope statement (only in-stock competitors are counted, landed price basis), which tells the agent this is a benchmark/positioning operation. However, there is no explicit 'use this when...' guidance, no mention of when a simpler alternative suffices, and no prerequisites stated.

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