Skip to main content
Glama

BRAINIAC Portfolio Analytics

Look-through allocation x-ray

portfolio-analytics_allocation-xray
Read-onlyIdempotent

Aggregate caller-supplied fund look-through holdings by asset class, sector, region and top underlying positions. Price $0.03 USDC. POST /api/v1/portfolio-analytics/allocation-xray. 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": {
      "positions": "<positions>"
    },
    "name": "portfolio-analytics_allocation-xray"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNotop, integer, from 1 to 100. Required.
positionsYespositions, array. Required.

Output Schema

NameRequiredDescriptionDefault
totalNototal. Number.
sourcesNosources. Array.
byRegionNobyRegion. Object.
bySectorNobySector. Object.
limitationsNolimitations. Array.
byAssetClassNobyAssetClass. Object.
topUnderlyingNotopUnderlying. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open world), the description discloses the paid-call mechanic: $0.03 USDC, the POST endpoint, and critically that an unpaid call returns x402 payment terms without executing the analysis. That last point is essential behavior an agent cannot infer from annotations or schema.

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 purpose, then cost, then endpoint, then payment failure behavior. Every sentence carries information, though the bare endpoint path is the least valuable for an agent deciding whether to call.

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 the payment/auth prerequisite is covered explicitly. Remaining gap is minor: no statement about input size limits or what happens with positions lacking lookThrough data.

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 baseline is 3, but the description adds genuine meaning: it states that assetClass, sector, region and the top-N underlying positions are the aggregation axes, which explains what the nested position fields and the 'top' parameter are actually for. It does not cover syntax details like weight normalization or how otherWeight interacts with lookThrough.

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 opens with a specific verb and resource: 'Aggregate caller-supplied fund look-through holdings', and names the grouping dimensions (asset class, sector, region, top underlying positions). This clearly separates it from siblings like brinson-attribution or correlation-matrix, though it never explicitly names an alternative.

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 implied by the described aggregation behavior and the 'caller-supplied holdings' framing, which tells an agent it must bring its own position data. There is no explicit when-to-use / when-not-to-use statement or named alternative among the many portfolio-analytics siblings.

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