Skip to main content
Glama
screener-mcp
by LogeshR15

get_portfolio

Read-only

View your portfolio with live prices, P&L, and per-holding weight. Computes invested value, current value, gain/loss, and position weights from Screener.in.

Instructions

View your portfolio with live prices, P&L, and per-holding weight.

Fetches the current price for each holding from Screener.in and computes invested value, current value, gain/loss (₹ and %), and each position's weight in the total portfolio.

Examples: get_portfolio()

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value on top by disclosing the external dependency on Screener.in and the exact derived values computed (invested value, current value, gain/loss in ₹ and %, position weight). It stops short of noting latency, failure behavior when a price is unavailable, or currency assumptions beyond the ₹ symbol.

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 purpose and computed fields are front-loaded in two tight sentences with no filler. The trailing "Examples: get_portfolio()" block is essentially dead weight for a zero-argument tool and slightly dilutes the otherwise efficient structure.

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 no-parameter, read-only tool with an output schema present, the description covers everything an agent needs: what it returns, where the prices come from, and that it is a pure read. Return-value formatting is correctly left to the output schema rather than duplicated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is a bare empty object, and the description correctly adds no parameter narrative that would be redundant.

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 names a specific verb and resource ("View your portfolio") and enumerates the outputs: live prices, P&L, and per-holding weight. It is unambiguously a read operation, which naturally separates it from the sibling mutations add_portfolio_stock, remove_portfolio_stock, and update_portfolio_stock.

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 by the word "View" and by the fact that the tool is read-only; the description never states when to reach for this versus the add/remove/update portfolio tools or when a fresh price fetch is warranted. The "Examples:" block shows only the zero-argument call syntax and adds no selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.