Skip to main content
Glama
screener-mcp
by LogeshR15

remove_portfolio_stock

DestructiveIdempotent

Remove a stock holding entirely from a portfolio to record a full exit and keep P&L tracking accurate.

Instructions

Remove a holding entirely from the portfolio (full exit).

Examples: remove_portfolio_stock("YESBANK")

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": {
      "symbol": "<symbol>"
    },
    "name": "remove_portfolio_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description's one added behavioral fact is that the removal is total ("entirely", "full exit") rather than partial, which is genuinely useful but thin; nothing about irreversibility, confirmation, or behavior on a missing 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?

One front-loaded sentence with the key scope qualifier, followed by a short example. Minimal and efficient, though the example is somewhat redundant with the sentence and adds only format 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?

An output schema exists, so return values need no explanation, and the tool has only one parameter. Still, for a destructive mutation it omits meaningful edge-case behavior (symbol not held, partial lots, effects on portfolio totals), leaving the agent to infer consequences of a hard-to-undo action.

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 0%, so the description carries the burden for the single `symbol` parameter. The example remove_portfolio_stock("YESBANK") usefully shows the expected value format as an uppercase ticker, but it never states whether company names are accepted, case sensitivity, or what an invalid symbol does.

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?

States a specific verb and resource ("Remove a holding entirely from the portfolio") plus a scoping qualifier ("full exit") that implicitly separates it from update_portfolio_stock, which would adjust rather than delete. An agent can distinguish add/update/remove without opening schemas, though no sibling is named explicitly.

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?

"Entirely (full exit)" hints that this is for closing a position rather than trimming it, which is useful context against update_portfolio_stock. However, there is no explicit when-to-use statement, no mention of the alternative tool by name, and no guidance on what happens when the symbol is not held.

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