Skip to main content
Glama

BRAINIAC Equity Analytics

Compute standard financial ratios

equity-analytics_financial-ratios
Read-onlyIdempotent

Profitability, liquidity, leverage, efficiency and valuation ratios from caller-supplied statements and an optional price. Missing fields yield null metrics; division by zero is reported. Price $0.03 USDC. POST /api/v1/equity-analytics/financial-ratios. 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": {
      "statements": "<statements>"
    },
    "name": "equity-analytics_financial-ratios"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNounit, string, length 1 to 64. Required.USD thousands
priceNoprice, number. Optional.
statementsYesstatements, array. Required.

Output Schema

NameRequiredDescriptionDefault
unitNounit. String.
periodsNoperiods. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses meaningful behavioral traits: missing fields return null metrics rather than failing, division by zero is reported, and the endpoint is disclosed. It also explains the payment gate — $0.03 USDC, an unpaid call returns x402 terms and does not execute — which tells the agent to expect a payment handshake instead of results on a first attempt.

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?

Four tight sentences: what it computes, edge-case behavior, cost, then transport and payment gating. The endpoint line is slightly low-value compared to the rest, but nothing is wasted or front-loaded incorrectly.

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 structures need no explanation, and the description still covers the two things the schema cannot: null-on-missing and division-by-zero reporting, plus the payment flow. Complete enough to call correctly; only the pricing unit/denomination implications of 'unit' are left unaddressed.

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 parameter definitions already carry field-level meaning. The description only clarifies that statements are supplied by the caller and that price is optional, which is essentially a restatement of the required/optional structure already in the schema.

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 the exact output categories (profitability, liquidity, leverage, efficiency, valuation) and the inputs that produce them (caller-supplied statements plus an optional price), which clearly separates it from focused single-metric siblings like dupont-analysis or altman-z-score. It never names an alternative explicitly, so it stops just short of top marks.

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 rather than stated: an agent can infer it should call this when it has full statements and wants the broad ratio set, and that price is optional for valuation ratios. There is no explicit when-not or named alternative (e.g. use peer-multiples instead when only comparables exist).

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