Skip to main content
Glama

BRAINIAC Equity Analytics

OLS equity beta vs a benchmark

equity-analytics_beta-regression
Read-onlyIdempotent

Align asset and benchmark closes, compute simple returns at daily, weekly or monthly frequency, and return OLS beta, alpha, R², standard error and optional Blume-adjusted beta. Price $0.03 USDC. POST /api/v1/equity-analytics/beta-regression. 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": {
      "assetPrices": "<assetPrices>",
      "benchmarkPrices": "<benchmarkPrices>"
    },
    "name": "equity-analytics_beta-regression"
  }
}

Input Schema

NameRequiredDescriptionDefault
frequencyNofrequency, string, one of daily, weekly, monthly. Required.daily
assetPricesYesassetPrices, array. Required.
blumeAdjustNoblumeAdjust, boolean. Required.
benchmarkPricesYesbenchmarkPrices, array. Required.

Output Schema

NameRequiredDescriptionDefault
nNon. Number.
r2Nor2. Number.
betaNobeta. Number.
alphaNoalpha. Number.
sourcesNosources. Array.
stdErrBetaNostdErrBeta. Number.
limitationsNolimitations. Array.
adjustedBetaNoadjustedBeta. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations that already establish read-only, idempotent, open-world, and non-destructive behavior, the description adds important operational context: pricing at $0.03 USDC, the POST endpoint, and that an unpaid call returns x402 payment terms without running the computation. It does not cover deeper edge cases such as minimum observation requirements or missing-date handling.

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?

The description is concise and front-loaded: the core computation comes first, followed by price, endpoint, and unpaid-call behavior. Every sentence adds relevant information without repetition.

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 regression endpoint with four parameters, an output schema, and complete schema descriptions, the definition covers the core computation, key outputs, payment terms, and unpaid behavior. It leaves minor gaps around data-sufficiency requirements and alignment edge cases, but is otherwise complete for correct invocation.

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. The description adds meaningful semantics by explaining that assetPrices and benchmarkPrices are aligned closes, that returns are simple returns, that frequency controls daily/weekly/monthly return computation, and that blumeAdjust enables optional Blume-adjusted beta.

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?

The description states a specific computation: aligning asset and benchmark closes, computing simple returns, and returning OLS beta, alpha, R², standard error, and optional Blume-adjusted beta. This is a clear verb-and-resource definition that distinguishes it from sibling equity-analytics tools such as WACC or Altman Z-score.

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 description implies usage when an agent has paired asset and benchmark close series and needs an OLS beta estimate, including daily, weekly, or monthly frequency. However, it does not explicitly say when not to use it or name alternative tools for related tasks.

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