Skip to main content
Glama

BRAINIAC Equity Analytics

Dividend yield, payout, coverage and CAGR

equity-analytics_dividend-metrics
Read-onlyIdempotent

Compute trailing yield, payout ratio, FCF coverage and DPS CAGR from a price and a dividends-per-share series. Price $0.02 USDC. POST /api/v1/equity-analytics/dividend-metrics. 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": {
      "price": "<price>",
      "dividendsPerShare": "<dividendsPerShare>"
    },
    "name": "equity-analytics_dividend-metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
epsNoeps, number. Optional.
priceYesprice, number. Required.
fcfPerShareNofcfPerShare, number. Optional.
dividendsPerShareYesdividendsPerShare, array. Required.

Output Schema

NameRequiredDescriptionDefault
cagrNocagr. Number.
yieldNoyield. Number.
sourcesNosources. Array.
fcfCoverageNofcfCoverage. Number.
limitationsNolimitations. Array.
payoutRatioNopayoutRatio. 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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: a $0.02 USDC x402 cost and the fact that an unpaid call returns payment terms instead of executing — critical context an agent cannot get from structured fields.

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: computation, price, endpoint, and payment-failure behavior, all front-loaded with no filler. The endpoint path is mildly incidental but plausibly useful for invocation context, so it is not pure waste.

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?

For a paid, read-only analytics tool with a full output schema, the description covers inputs, outputs, cost, and payment semantics. Return-value shape needs no explanation because an output schema exists; only cross-tool routing guidance is missing.

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% and each field (price, dividendsPerShare with year/dps, optional eps and fcfPerShare) is documented in the schema. The description only restates that price and a DPS series are required, adding no format or constraint detail beyond what the schema already provides.

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 first sentence names a specific verb ('Compute') and enumerates the exact metrics produced (trailing yield, payout ratio, FCF coverage, DPS CAGR) plus the required inputs, so an agent knows precisely what the tool returns. It does not explicitly contrast itself with siblings like total-return-series or financial-ratios, which keeps it from a 5.

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 stated inputs (price plus a dividends-per-share series) and the listed outputs, and the payment behavior clarifies a prerequisite. However, there is no explicit when-to-use guidance or exclusion naming an alternative tool for related computations.

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