Skip to main content
Glama

Grade a portfolio

grade_portfolio
Read-onlyIdempotent

Runs the free Portfolio Optimizer Pro checkup on a list of holdings and weights. Returns the A+ to F structural grade, the 0-100 score, any structural ceiling (cap) applied, each factor's sub-score with its measured fact, the top findings that held the grade down, the price-history dates used, a disclaimer and full_breakdown_url, a link that opens the same graded checkup on the website. Grades describe diversification, cost and past risk; they are educational, not advice or a forecast. Unknown tickers are listed in unknown_tickers, never guessed.

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": {
      "holdings": "<holdings>"
    },
    "name": "grade_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsYesThe portfolio: 1 to 30 holdings, each ticker once, with its weight.

Output Schema

NameRequiredDescriptionDefault
dataYes
gradeYesLetter grade A+ to F, or "Not graded".
scoreYes0–100 structural score.
factorsYesEach graded factor, worst first.
noticesYes
disclaimerYes
cap_appliedYesLowest structural ceiling that applies, or null.
risk_profileYes
top_findingsYesTop 1–3 things that held the grade down.
holdings_gradedYes
methodology_urlYes
unknown_tickersYesTickers with no usable price history; they were left out and the grade is capped as partial.
full_breakdown_urlYesOpens the free checkup already graded for these holdings, with the full explanation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world, and the description adds meaningful behavioral context beyond that. It discloses the educational nature of grades, that they are not advice or forecasts, what the grade covers, and that unknown tickers are listed rather than guessed.

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?

The description is front-loaded with the core action and remains reasonably tight throughout. The long enumeration of return fields somewhat duplicates the output schema, which slightly reduces conciseness, but it does not bury the essential purpose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one parameter, rich annotations, and an output schema, the description covers everything an agent needs to call it correctly. It explains purpose, output meaning, educational limitations, and unknown-ticker handling without requiring the agent to infer those behaviors.

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?

The input schema is fully described and already covers ticker format, weight normalization, and the 1-to-30 holding limit. The description restates that the tool takes a list of holdings and weights but adds little parameter-specific meaning beyond the schema, aside from input-validation behavior for unknown tickers.

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 states a specific action and resource: it runs a Portfolio Optimizer Pro checkup on a list of holdings and weights and returns a structural grade. That is clear enough to distinguish a grading tool from a generic lookup, but it does not explicitly contrast itself with siblings such as check_overlap or explain_grading.

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 describing the tool as a checkup on a holdings list, but there is no explicit guidance about when to use this tool rather than check_overlap, explain_grading, or fund_fee_cost. It also does not state when-not to use it. Adequate but clearly missing routing 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