Skip to main content
Glama

BRAINIAC Portfolio Analytics

Brinson-Fachler attribution

portfolio-analytics_brinson-attribution
Read-onlyIdempotent

Allocation, selection and interaction effects by segment for one or more periods, with optional Carino linking. Price $0.04 USDC. POST /api/v1/portfolio-analytics/brinson-attribution. 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": {
      "periods": "<periods>"
    },
    "name": "portfolio-analytics_brinson-attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkingNolinking, string, one of carino, none. Required.carino
periodsYesperiods, array. Required.
normalizeWeightsNonormalizeWeights, boolean. Required.
allowNegativeWeightsNoallowNegativeWeights, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
totalsNototals. Object.
sourcesNosources. Array.
segmentsNosegments. Array.
limitationsNolimitations. Array.
activeReturnNoactiveReturn. Number.
benchmarkReturnNobenchmarkReturn. Number.
portfolioReturnNoportfolioReturn. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations declare safe, read-only, idempotent behavior, and the description adds genuinely non-obvious operational facts: a $0.04 USDC price, the POST /api/v1/portfolio-analytics/brinson-attribution transport, and the crucial gate that an unpaid invocation returns x402 payment terms instead of results. That last point is exactly the kind of failure mode an agent needs pre-warned so it does not treat a payment challenge as a computed result.

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 tight sentences: what is computed first, then the commercial/transport facts, then the payment gate. Every clause carries information an agent cannot get from the structured fields, and the most consequential constraint (no execution without payment) is placed last for emphasis.

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?

An output schema exists, so return values need not be described, and the input schema is fully annotated. Combined with the payment and endpoint details, an agent has enough to call it correctly. It could still be stronger by noting that weights must sum sensibly unless normalizeWeights is set, or what happens with the interaction term when rb/wp are zero.

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%, so the schema already documents periods, the nested segment fields (name/wp/wb/rp/rb), linking, normalizeWeights and allowNegativeWeights. The description adds only the notion that Carino linking is optional and pairs it with periods; it says nothing about weight normalization or negative-weight behavior beyond what the schema states, so baseline 3 applies.

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?

States a specific verb-and-resource: allocation, selection and interaction effects by segment across one or more periods, plus an optional Carino linking mode. That is far more precise than the bare title and lets an agent recognize this as the Brinson-Fachler decomposition. It stops short of naming when a sibling (e.g. allocation-xray or performance-twr-mwr) would be the better pick.

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?

There is no guidance on when to choose this decomposition over the other performance/attribution siblings, and no stated prerequisites such as needing segment-level weights and returns for each period. The only contextual guidance is payment-related (an unpaid call does not execute), which is operational rather than selection guidance.

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