USERDATA

add_to_list

Adds a ticker to a named watchlist or peer group with a recorded reason, helping users track and organize research candidates.

Instructions

Puts a ticker on a watchlist or peer group.

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": {
      "list_name": "<list_name>",
      "ticker": "<ticker>",
      "reason_text": "<reason_text>"
    },
    "name": "add_to_list"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes
`list_name`	Yes
`reason_text`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and falls well short: it does not state that a mandatory rationale (reason_text) is required, whether the operation is idempotent, what happens on duplicate tickers, or whether permissions or a pre-existing list are needed. Only the bare mutation intent is conveyed.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler or redundancy. It is efficient, though the terseness contributes to the specification gaps noted elsewhere rather than being a structural flaw in itself.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but for a three-parameter mutation tool with no annotations and 0% schema coverage the description is far too thin. At minimum it should explain the required reason, list-name validity, and duplicate behavior.

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

Parameters2/5

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

Schema description coverage is 0% across three required parameters, so the description must compensate. It implies ticker and list_name (watchlist or peer group), but gives no format, no hint about valid list names, and leaves the required reason_text entirely unexplained — a significant omission for a mandatory argument.

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?

The description names a specific verb and resource: 'Puts a ticker on a watchlist or peer group,' which is clearly the inverse of the sibling remove_from_list and distinct from create_list. It is unambiguous about what gets added to what, though it does not explicitly name or contrast those siblings.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention that the target list must already exist (versus creating one with create_list), and no guidance on how this relates to add_note or tag for similar annotation tasks. The agent is left to infer the entire selection context from the name alone.

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