Skip to main content
Glama

BRAINIAC Portfolio Analytics

Factor regression of excess returns

portfolio-analytics_factor-regression
Read-onlyIdempotent

OLS of portfolio excess returns on caller-supplied factors with intercept, betas, alpha and optional Newey-West standard errors. Price $0.04 USDC. POST /api/v1/portfolio-analytics/factor-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": {
      "returns": "<returns>",
      "factors": "<factors>"
    },
    "name": "portfolio-analytics_factor-regression"
  }
}

Input Schema

NameRequiredDescriptionDefault
factorsYesfactors, object. Required.
returnsYesreturns, array. Required.
riskFreeNoriskFree, value. Required.
neweyWestLagsNoneweyWestLags, integer, from 0 to 100. Required.
periodsPerYearNoperiodsPerYear, number. Required.

Output Schema

NameRequiredDescriptionDefault
nNon. Number.
betasNobetas. Array.
alphaSeNoalphaSe. Number.
sourcesNosources. Array.
rSquaredNorSquared. Number.
limitationsNolimitations. Array.
alphaPerPeriodNoalphaPerPeriod. Number.
alphaAnnualizedNoalphaAnnualized. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a $0.04 USDC charge, the POST endpoint, and the x402 payment-terms short-circuit on unpaid calls. It does not state failure modes (e.g., length mismatches) or rate limits.

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, front-loaded with the method, then cost/endpoint, then the payment-gating caveat. No filler or repetition of the title.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile; the description fills the remaining gaps (cost, endpoint, payment behavior). It could still note input-alignment expectations for a nested factor object and returns array, but overall it is adequate for a 5-parameter read-only tool.

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 coverage is 100%, so the schema already documents every parameter, including defaults and bounds. The description only reinforces that factors are caller-supplied and that Newey-West errors are optional (lags default 0), which is marginal added meaning over the structured fields.

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?

Names the exact statistical operation ('OLS of portfolio excess returns on caller-supplied factors') and enumerates the produced quantities (intercept, betas, alpha, optional Newey-West errors). That is specific enough to separate it from siblings like correlation-matrix or risk-metrics, but it never explicitly routes against them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when this regression is the right choice versus alternatives such as performance-twr-mwr or risk-metrics, and no prerequisites about data alignment (equal-length returns, factor arrays). The only situational guidance is payment-related: an unpaid call returns x402 terms and does not run.

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