Skip to main content
Glama

BRAINIAC Portfolio Analytics

Project long-run fee drag

portfolio-analytics_fee-drag-project
Read-onlyIdempotent

Compare terminal wealth with and without expense ratios, advisory fees and loads under multiplicative or subtractive fee methods. Price $0.02 USDC. POST /api/v1/portfolio-analytics/fee-drag-project. 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": {
      "initial": "<initial>",
      "years": "<years>",
      "grossReturn": "<grossReturn>"
    },
    "name": "portfolio-analytics_fee-drag-project"
  }
}

Input Schema

NameRequiredDescriptionDefault
feesNofees, array. Required.
yearsYesyears, integer, from 1 to 100. Required.
initialYesinitial, number. Required.
feeMethodNofeeMethod, string, one of multiplicative, subtractive. Required.multiplicative
frontLoadNofrontLoad, number, from 0 to 1. Required.
grossReturnYesgrossReturn, number. Required.
includeByYearNoincludeByYear, boolean. Required.
annualContributionNoannualContribution, number. Required.

Output Schema

NameRequiredDescriptionDefault
byYearNobyYear. Array.
feeDragNofeeDrag. Number.
sourcesNosources. Array.
feeDragPctNofeeDragPct. Number.
limitationsNolimitations. Array.
terminalNoFeesNoterminalNoFees. Number.
terminalWithFeesNoterminalWithFees. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description nonetheless adds material context the annotations do not cover: a $0.02 USDC price, the x402 payment prerequisite, and the specific consequence that an unpaid call returns payment terms and does not execute. Response shape is left to the output 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?

Three tight sentences, front-loaded with the computational purpose before pricing and payment mechanics. The raw endpoint path is low-value metadata, but nothing is padded or restated.

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 and rich annotations, the description only needs to cover purpose, semantics and the payment gate, all of which it does. Minor gaps remain around how annualContribution and includeByYear change the result, though those defaults are documented in the schema.

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 names, ranges and defaults, putting this at the baseline. The description does add real meaning for the feeMethod enum (multiplicative vs. subtractive) and clarifies that fees covers expense ratios, advisory fees and loads, which the schema's generic name/rate items do not convey.

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?

The first sentence states a concrete comparison (terminal wealth with vs. without fees) and enumerates the fee types covered, plus the multiplicative/subtractive method dimension. No sibling in the catalog computes fee drag, so an agent can disambiguate it from performance-twr-mwr or rebalance-trades on the description alone.

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: an agent can infer this is the tool for modeling the long-run cost of fees on a portfolio. There is no explicit when-to-use guidance, no exclusion of near-neighbors (e.g., performance attribution vs. fee projection), and no statement of prerequisites beyond the payment note.

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