Skip to main content
Glama

Check Portfolio

check_portfolio

Calculate confirmed portfolio risk within the supported ticker coverage. All US exchange-listed common stocks, ADRs and ETFs on NYSE, Nasdaq and NYSE American can be submitted. Results require verified data; a price lookup does not expand model coverage. Preparing your result. The estimated time appears below; it may change. Your allowance is used only after a successful result. Preserve unavailable values and follow the returned next steps. Do not invent calculations, substitute a generic analysis, or provide trading or options instructions. Covered tickers only: Only tickers listed in /bench-live/coverage.json return results; other tickers return outside_coverage. May persist a calculation job, usage record or saved settings. Successful calculations may consume account allowance. Repeating the request may have side effects.

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": {
      "input": "<input>"
    },
    "name": "check_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
languageNo
confirmedNo
total_usdNo
request_idNoClient idempotency key for a retry of this exact request.
confirmation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive, closed-world operation; the description goes meaningfully beyond that by disclosing persistence of a calculation job, usage record or saved settings, allowance consumption only on success, possible side effects on repeat, and a confirmation/next-steps flow. Minor boilerplate ("Preparing your result. The estimated time appears below") dilutes but does not undermine the disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The strongest content is front-loaded in sentence one, but the body is a rambling mix of coverage rules, allowance notes, and UI-flavored boilerplate such as "Preparing your result. The estimated time appears below; it may change." Several sentences could be deleted without losing any decision-relevant information.

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

Completeness3/5

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

For a 6-parameter, state-mutating tool with no output schema and very thin schema descriptions, the definition covers eligibility, confirmation, allowance and side effects but leaves the input payload shape unexplained. An agent can decide whether to call it but would need to read the schema closely to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description needs to carry parameter meaning, and it largely does not. The central `input` parameter (a string OR an array of up to 100 {symbol, unit, value} objects) is never explained, nor are `total_usd`, `confirmed`, `confirmation_id`, or `language`; only vague hints ("confirmed portfolio risk", "Preserve unavailable values") gesture at them.

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 ("Calculate confirmed portfolio risk") and scopes it to supported ticker coverage, which is enough to separate it from siblings like analyze_holdings or get_pod_portfolio. It does not explicitly name an alternative tool, so differentiation is implicit 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 Guidelines3/5

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

It gives a usable eligibility rule ("Only tickers listed in /bench-live/coverage.json return results; other tickers return outside_coverage") and warns that a price lookup does not expand coverage. However, there is no guidance on when to choose this over the many adjacent analysis tools, nor any prerequisite/preparation instructions for the caller.

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