Skip to main content
Glama
TickerDB

TickerDB

Official

add_watchlist_tickers

Idempotent

Add stock, ETF, or crypto tickers to a shared TickerDB watchlist to track score, price moves, earnings, and other market changes.

Instructions

Add tickers to the user's TickerDB watchlist (one per account, shared with the website's Track buttons and Claude/ChatGPT watchlist links). Idempotent: already-present tickers come back in already; unknown ones in unknown. No ticker limit; free. Then get_watchlist_changes (call_tool) reports what changed for them since the last check: score, upside and downside potential, earnings, big price moves, trend changes, RSI oversold, volume spikes, insider trades, analyst changes, serious 8-K filings and dividend cuts.

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": {
      "tickers": "<tickers>"
    },
    "name": "add_watchlist_tickers"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesTicker symbols, e.g. ["NVDA", "AMD"]. Up to 50.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool's result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description earns credit for making that concrete: already-present tickers return in 'already' and unknowns in 'unknown'. It also discloses cross-surface effects (shared with the website's Track buttons and other watchlist links) and the absence of a ticker limit or cost, which annotations do not cover.

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

Conciseness3/5

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

The purpose and idempotency points are front-loaded and useful, but the final sentence enumerating score, upside/downside, RSI, 8-Ks, dividend cuts and more is a promotional feature list that does not help an agent invoke this tool correctly.

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 one-parameter write tool with an output schema, the definition covers mutation scope, idempotency, limits, and cost — everything needed to call it safely. The trailing pointer to a sibling's capabilities is extra but harmless; nothing essential 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 there is a single, well-documented array parameter with its own example and bound, so the baseline is 3. The description adds no format semantics the schema lacks, such as case sensitivity or exchange-suffix handling.

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 — 'Add tickers to the user's TickerDB watchlist' — and immediately clarifies the scope ('one per account, shared with the website's Track buttons'), which no sibling name alone would convey. An agent can tell this apart from remove_watchlist_tickers 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 clear context for use (adding tickers, no limit, free) and points to get_watchlist_changes via call_tool as the follow-up. It does not explicitly state when to use remove_watchlist_tickers instead, so the exclusion half of the guidance is missing.

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