Skip to main content
Glama

List My Stock Watchlist

list_watchlist
Read-onlyIdempotent

List the tickers on the user's LuBot watchlist.

Returns each ticker and when it was added, oldest first. Use this when the user asks which stocks they are watching. Don't use it for holdings (use list_portfolio).

Limits: requires sign-in; up to 200 tickers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tickersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / description
      Previous value: -"`list_watchlist` structured result (MARKET-17 S6-4 outputSchema).\n\nSame JSON as before: {\"tickers\": [...]}."New value: +"The tickers on the user's watchlist."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "Ticker": {
      +      "additionalProperties": false,
      +      "description": "A stock ticker in the caller's watchlist.",
      +      "properties": {
      +        "added_at": {
      +          "anyOf": [
      +            {
      +              "format": "date-time",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "Added At"
      +        },
      +        "symbol": {
      +          "maxLength": 10,
      +          "minLength": 1,
      +          "title": "Symbol",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "symbol"
      +      ],
      +      "title": "Ticker",
      +      "type": "object"
      +    }
      +  },
      +  "additionalProperties": false,
      +  "description": "`list_watchlist` structured result (MARKET-17 S6-4 outputSchema).\n\nSame JSON as before: {\"tickers\": [...]}.",
      +  "properties": {
      +    "tickers": {
      +      "items": {
      +        "$ref": "#/$defs/Ticker"
      +      },
      +      "title": "Tickers",
      +      "type": "array"
      +    }
      +  },
      +  "title": "WatchlistResult",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes further by disclosing the ordering of results (oldest first), an authentication prerequisite, and a hard cap of 200 tickers. Those are exactly the operational constraints an agent needs before calling, and none of them are derivable from the annotations.

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?

Four short sentences, each doing distinct work: purpose, return shape, trigger, exclusion, then limits. The purpose and trigger are front-loaded and there is no filler.

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?

For a zero-parameter read tool with a full annotation set and an output schema, the description covers everything remaining: what is returned, in what order, who may call it, and how large it can get. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the empty schema. Baseline applies; no value is added or lost here.

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?

The description names a specific verb and resource ("List the tickers on the user's LuBot watchlist") and explicitly separates it from the holdings sibling ("Don't use it for holdings (use list_portfolio)"). An agent can pick this tool without inspecting any schema.

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

Usage Guidelines5/5

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

It states the positive trigger ("when the user asks which stocks they are watching") and an explicit exclusion with the correct alternative (holdings → list_portfolio). Both the when and the when-not are present, so nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources