Skip to main content
Glama

check_portfolio

Read-onlyIdempotent

Check the person's own portfolio in numbers, on two years of daily returns, on a card: their mix among every other way to split the same holdings (the efficient frontier, the least-risk and best-ratio mixes and how far theirs is from the edge), which holdings move together, where the swings come from, the same holdings split four other ways (mean-variance, risk parity, calmer weigh more, a score) and where $1 of the mix could be in a year.

    Use it when the person gives their holdings and asks for them to be analysed or checked ("here is my
    portfolio: AAPL 20%, MSFT 10% ...", "analyse my holdings"). It reads the past and says nothing about what to
    do: begin your answer with the answer's `line` as it is, then at most one sentence; the card shows the rest.
    Five holdings at the least and 30 at the most, none above half of the money; weights that do not add to 100
    are scaled, and a list without weights is weighed equally.

    Args:
        holdings: Each holding's ticker or company name, and its weight in percent where the person gave one.

    The answer gives `line` (say it first) and `card` (what the card shows), or `message` when the check stays in
    QuanterLab.
    

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": "check_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds real context beyond them: the two-year daily-return basis, the input normalization rules, and the fact that the response may instead be a `message` when "the check stays in QuanterLab" — an important gate the agent would otherwise not anticipate. The required answer-opening behavior is also disclosed.

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?

Well organized into purpose, when-to-use, args, and return-shape blocks, so an agent can scan it. The first sentence is an overstuffed run-on with many stacked clauses, and "on a card" / "the card shows the rest" restate the same idea in two places, costing some tightness without obscuring meaning.

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 single-parameter read-only analysis tool with no output schema, the description supplies everything needed: what is computed, the data window, input validation constraints, the required response framing, and the alternate `message` return path. Nothing an agent needs in order to call it correctly is missing.

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 reported as 0% at the top level, but the description compensates well: the Args section defines each entry as a ticker or company name plus an optional weight in percent, and adds semantics the schema lacks entirely — weights not summing to 100 are scaled, an unweighted list is weighed equally, minimum 5 and maximum 30 holdings, and no single holding above 50%. It does not explain ticker resolution failure behavior, which is the only notable gap.

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 opening sentence names a specific verb and resource ("Check the person's own portfolio in numbers, on two years of daily returns, on a card") and enumerates the exact analytics produced: frontier position, correlation, risk contribution, four alternative weightings, and a one-year dollar range. That is far more specific than the title alone, though it never names a sibling tool to contrast against, so differentiation is inferred from the described content rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the trigger condition with concrete user phrasings ("here is my portfolio: AAPL 20%, MSFT 10% ...", "analyse my holdings") and explicitly bounds scope: "It reads the past and says nothing about what to do." Hard input constraints (5-30 holdings, none above half the money, weight normalization, equal weighting when absent) tell the agent when a call is valid, and the instruction to lead the answer with `line` tells it how to present the result.

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