Skip to main content
Glama
TickerDB

TickerDB

Official

remove_watchlist_tickers

DestructiveIdempotent

Remove selected ticker symbols from a TickerDB watchlist and return any symbols that were not present, so you can keep the list accurate.

Instructions

Remove tickers from the user's TickerDB watchlist. Idempotent: tickers not on it come back in missing. Free.

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": "remove_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 destructive=true and idempotentHint=true; the description goes beyond them by explaining the idempotency mechanism (tickers not present are reported in 'missing') and disclosing that the call is free. It stops short of covering auth requirements or any side effects beyond list membership.

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 short clauses, each carrying distinct information (action, idempotent return behavior, cost), with the core action front-loaded. Nothing is redundant.

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 mutation tool with full schema coverage, an output schema, and annotations covering the safety profile, this is nearly complete. Only minor context such as authentication expectations or behavior when every ticker is absent 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% for the single parameter, and the schema already documents the symbol format and the 50-item cap, so the description adds no parameter meaning beyond it. Baseline 3 is appropriate.

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 with scope: 'Remove tickers from the user's TickerDB watchlist.' The verb 'Remove' cleanly separates it from the sibling add_watchlist_tickers without needing to name it.

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 implied by the purpose (use it to take symbols off a watchlist), and 'Free' hints that cost shouldn't be a barrier, but there is no explicit when-to-use/when-not guidance or named alternative for the inverse operation.

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