Skip to main content
Glama
Sign In

Stock Compass

by io.github.Stock-Compass
OverviewDiscussionsAdmin

Add to watchlist

add_to_watchlist

Adds a stock to the watchlist. The stock has to exist at its market's quote source, and the plan's watchlist limit applies. 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": "add_to_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.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false; the description adds the non-obvious two-phase preview/commit protocol and validation preconditions, which is real behavioral value. It does not describe error behavior, what the preview response contains, or how long a preview_id stays valid (relevant given idempotentHint=false).

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 tight sentences, front-loaded with purpose, then constraints, then the call protocol. Nothing is padded and the most decision-relevant fact (nothing changes without preview_id) is easy to find.

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

Completeness4/5

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

For a state-changing tool with no output schema, the description covers the essential mechanics: preconditions and the two-step commit. It could say more about what the preview returns and how to recover if a preview_id is stale, but an agent can call it correctly from this text.

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?

With 100% schema description coverage, market, ticker, and preview_id are already documented, including the note that omitting preview_id changes nothing. The description restates that same preview_id semantics rather than adding new detail, so the baseline 3 applies.

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 ('Adds a stock to the watchlist') plus the constraints that govern success (stock must exist at its quote source, plan watchlist limit). It is clearly distinguishable from remove_from_watchlist by name and verb, 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 Guidelines4/5

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

Gives concrete when/how guidance for the trickiest part of usage: calling without preview_id changes nothing, calling again with the same arguments plus preview_id commits. Preconditions for use are also stated. It does not name alternatives such as remove_from_watchlist or get_watchlist for verification.

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