Skip to main content
Glama

BRAINIAC Equity Analytics

Back-adjust prices for splits and dividends

equity-analytics_corporate-action-adjust
Read-onlyIdempotent

Apply split and cash-dividend factors backwards through a price series (CRSP-style multiplicative dividends) and return adjusted closes, volumes and cumulative factors. Price $0.03 USDC. POST /api/v1/equity-analytics/corporate-action-adjust. 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": {
      "prices": "<prices>"
    },
    "name": "equity-analytics_corporate-action-adjust"
  }
}

Input Schema

NameRequiredDescriptionDefault
pricesYesprices, array. Required.
actionsNoactions, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
adjustedNoadjusted. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world. The description adds value beyond them: the payment gate and the concrete failure mode for unpaid calls ('returns x402 payment terms and does not run'), which an agent cannot infer from any annotation. It does not describe error behavior for malformed or unsorted input, but the payment behavior is the more consequential disclosure.

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, each earning its place: what it computes, what it costs, where it lives, and the failure mode. Function is front-loaded before the endpoint and payment details.

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-value explanation is not needed, and the annotation set plus a short description covers most of it. The remaining gap is the price-series precondition (ordering, whether dates must be ascending) that an agent would need for a correct call.

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% and the schema already enumerates the split/dividend union with ratio, amount and exDate. The description adds only the 'backwards through a price series' directionality, which is meaningful but thin; it does not explain how volumes are adjusted or what the cumulative factor refers to.

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?

States a specific verb (apply/back-adjust), specific resources (split and cash-dividend factors, price series) and the exact outputs (adjusted closes, volumes, cumulative factors). The 'CRSP-style multiplicative dividends' qualifier distinguishes the methodology from a simple additive adjustment.

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?

Gives the essential operational condition — the call costs $0.03 USDC and an unpaid call returns x402 payment terms without running — but never says when an agent should prefer this tool over, say, total-return-series or how to obtain the factor data or whether prices must be sorted. Usage context is implied by purpose only.

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