Skip to main content
Glama
Sign In

Stock Compass

by io.github.Stock-Compass
OverviewDiscussionsAdmin

Remove from watchlist

remove_from_watchlist
DestructiveIdempotent

Removes a stock from the watchlist, with its price alerts. A stock still held is refused until its sale is recorded. Sent without preview_id, it changes nothing and returns a preview of the change with a preview_id; sent again with the same arguments and that preview_id, it makes the change.

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": {
      "market": "<market>",
      "ticker": "<ticker>"
    },
    "name": "remove_from_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketYeshk = Hong Kong, us = United States, cn = China A-shares.
tickerYesFor example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).
preview_idNoThe preview_id that the same call without it returned. Without it, nothing is changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the substance those hints cannot convey: the collateral deletion of price alerts, the held-position refusal, and the exact two-phase preview-then-commit protocol including the requirement to resend identical arguments. This is precisely the added context the annotations leave open.

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

Conciseness5/5

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

Three sentences, each carrying distinct load: what is removed, when it is refused, and how to actually commit the change. The destructive scope is front-loaded before the procedural detail, so an agent skimming the first clause still learns what will be deleted.

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?

With no output schema, the description correctly compensates by describing what the keyless call returns (a preview plus a preview_id) rather than the exact payload shape. Combined with the precondition and the commit protocol, nothing an agent needs to call this destructively-but-safely is missing.

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 coverage is 100% and the schema already documents market, ticker formats, and that preview_id is the value returned by the same call without it. The description restates the preview_id contract at a process level but adds no new syntactic or format information beyond the field descriptions, so baseline 3 applies.

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?

States a specific verb and resource ('Removes a stock from the watchlist') and extends the scope to a secondary resource ('with its price alerts'), which is exactly the detail that separates it from add_to_watchlist and from the trade tools. An agent can identify the operation and its blast radius without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear precondition for refusal ('A stock still held is refused until its sale is recorded'), which tells the agent when this call will fail and what must precede it. It does not name sibling alternatives (e.g. delete_trade or record_trade) explicitly, so it stops just short of full when/when-not routing.

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

All Stock Compass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources