Skip to main content
Glama

BRAINIAC Portfolio Analytics

Tracking error and capture ratios

portfolio-analytics_tracking-error-capture
Read-onlyIdempotent

Tracking error, information ratio, up/down capture, batting average and optional active share versus a benchmark. Price $0.03 USDC. POST /api/v1/portfolio-analytics/tracking-error-capture. 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": {
      "portfolio": "<portfolio>",
      "benchmark": "<benchmark>"
    },
    "name": "portfolio-analytics_tracking-error-capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsNoholdings, object. Optional.
benchmarkYesbenchmark, array. Required.
portfolioYesportfolio, array. Required.
captureMethodNocaptureMethod, string, one of arithmetic, geometric. Required.arithmetic
periodsPerYearNoperiodsPerYear, number. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
upCaptureNoupCapture. Number.
activeShareNoactiveShare. Number.
downCaptureNodownCapture. Number.
limitationsNolimitations. Array.
trackingErrorNotrackingError. Number.
battingAverageNobattingAverage. Number.
informationRatioNoinformationRatio. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 bar is lower; the description still adds real behavioral context the annotations cannot convey: a $0.03 USDC price, the POST endpoint, and the fact that an unpaid call returns payment terms instead of executing. It stops short of describing output shape or failure modes beyond payment.

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 short sentences, front-loaded with the metric list, followed by price, endpoint, and the payment-failure behavior — no filler. Slightly telegraphic, but every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need no explanation, and the payment flow is covered. However, for a tool whose core inputs are two numeric arrays plus a nested holdings object, the description never clarifies how portfolio and benchmark series must align or what units they are in, which is the main remaining gap.

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 baseline is 3. The description adds only 'optional active share versus a benchmark' and says nothing about the meaningful choices in the schema, such as captureMethod (arithmetic vs geometric) or periodsPerYear, and the auto-generated schema text ('portfolio, array. Required.') leaves the array semantics (returns vs weights) unexplained.

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 specific metrics computed (tracking error, information ratio, up/down capture, batting average, optional active share) and states they are measured versus a benchmark, so the resource and operation are unambiguous. It does not explicitly contrast with siblings like risk-metrics or performance-twr-mwr, keeping it short of 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 only implied by the metric list; there is no explicit statement of when to prefer this over risk-metrics or performance-twr-mwr, nor any prerequisite beyond the payment note. The paid-call condition ('an unpaid call returns the x402 payment terms and does not run') is a genuine usage constraint that partially compensates.

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