Skip to main content
Glama
alpacahq

alpaca-mcp-server

Official
by alpacahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_watchlist_by_id

Replace an existing watchlist by ID, updating its name and full symbol list. Include all desired symbols, as any omitted assets are removed.

Instructions

Update an existing watchlist. IMPORTANT: this replaces the entire watchlist. You must include the symbols parameter with the full list of desired symbols, otherwise all assets will be removed.

Input Schema

NameRequiredDescriptionDefault
nameNoThe new watchlist name.
symbolsNoList of asset symbols to include in the watchlist. The existing assets will be replaced with the new list.
watchlist_idYeswatchlist id

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.0
    • changedInput schema / properties / symbols / items / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
  2. Changed4 schema fields changedv2.3.2
    • changedInput schema / properties / name / description
      Previous value: -"The watchlist name."New value: +"The new watchlist name."
    • changedInput schema / properties / symbols / description
      Previous value: -"List of asset symbols to include in the watchlist."New value: +"List of asset symbols to include in the watchlist. The existing assets will be replaced with the new list."
    • removedInput schema / properties / symbols / items / nullable
      Removed value: -true
    • changedInput schema / properties / symbols / items / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  3. Addedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it delivers the most important behavioral fact: the operation is a full replace, and omitting symbols wipes all assets. It does not cover permission requirements, reversibility, or response shape, but the destructive semantics are disclosed plainly.

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 sentences, front-loaded with the purpose and then the critical dependency. Every sentence earns its place; no filler.

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?

An output schema exists, so return values need not be described, and all three parameters are schema-documented. For an un-annotated mutation tool the description covers the destructive behavior well, though it is silent on auth requirements and whether the name field is preserved when omitted.

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?

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining the consequence of omitting symbols ('all assets will be removed'), which the schema's 'the existing assets will be replaced' phrasing does not make as explicit for the empty case. It adds little about name semantics (whether it is optional/preserved).

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+resource ('Update an existing watchlist') and immediately clarifies the replace-vs-append semantics, which is what distinguishes it from add_asset_to_watchlist_by_id and create_watchlist. It does not name those siblings explicitly, so it stops short of a 5.

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: this is the tool for wholesale replacement of a watchlist's contents, and it warns that symbols must be supplied in full. It does not explicitly route the agent to add_asset_to_watchlist_by_id for incremental additions, which would be the missing piece for a 5.

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

Deploy Server

Other Tools