Skip to main content
Glama

BRAINIAC Equity Analytics

Three- and five-step DuPont ROE

equity-analytics_dupont-analysis
Read-onlyIdempotent

Decompose ROE into net margin, asset turnover and equity multiplier, and optionally the five-step tax, interest and EBIT-margin path. Price $0.02 USDC. POST /api/v1/equity-analytics/dupont-analysis. 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": {
      "netIncome": "<netIncome>",
      "revenue": "<revenue>",
      "totalAssets": "<totalAssets>",
      "equity": "<equity>"
    },
    "name": "equity-analytics_dupont-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebtNoebt, number. Optional.
ebitNoebit, number. Optional.
equityYesequity, number. Required.
revenueYesnetIncome, number. Required.
netIncomeYesnetIncome, number. Required.
totalAssetsYestotalAssets, number. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
fiveStepNofiveStep. Object.
threeStepNothreeStep. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds material context those annotations cannot: a $0.02 USDC price, the endpoint, and crucially that an unpaid call returns x402 payment terms and does not execute. It does not state result caching or input-unit expectations, keeping it short of a 5.

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?

Front-loaded with what the tool computes, then cost, then endpoint and payment semantics in short declarative clauses. The raw POST path is arguably the least useful sentence, but it is compact and relevant for an agent that must construct a paid call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 structure needn't be described; the description instead covers the complexity that matters for this tool: dual decomposition modes and the payment precondition. Combined with the schema's required-field and exclusiveMinimum constraints, nothing essential for a correct call is missing beyond minor unit conventions.

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 the baseline is 3, but the schema descriptions are tautological ("ebit, number. Optional.") and the description adds real meaning by tying ebit and ebt to the five-step tax/interest/EBIT-margin decomposition. It still does not specify units (decimal vs percent) or whether netIncome/revenue must share a period with totalAssets/equity.

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?

"Decompose ROE into net margin, asset turnover and equity multiplier" names a specific verb and resource, and explicitly distinguishes the three-step from the optional five-step path. An agent can tell this apart from sibling ratio tools such as financial-ratios or piotroski-f-score without opening the schema.

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?

The description clarifies the mode selection: the five-step path is optional and evidently requires the optional ebit/ebt inputs, giving concrete context for when extra parameters pay off. It does not name an alternative tool or state when NOT to use it, so it stops short of full routing 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