Skip to main content
Glama

FinBridge

Add or Remove Watchlist Companies

manage_watchlist
DestructiveIdempotent

Add or remove a company from the user's watchlist. This changes saved preferences, not financial assets. Only remove deletes an entry.

action='add' and action='remove' each take one symbol and are idempotent: adding a company already on the list leaves it there, removing one that is not on the list is a no-op. Both report the resulting list size.

Not this tool for: holdings and cash (that is a portfolio — use get_portfolio / import_portfolio), or for any market data. The watchlist stores which companies the user follows, nothing about quantities, prices or returns.

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": {
      "action": "<action>"
    },
    "name": "manage_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes'add' and 'remove' each need a symbol.
symbolNoStock code, ticker or company name. Required for 'add' and 'remove'.

Output Schema

NameRequiredDescriptionDefault
nameNo
errorNo
totalNo
actionNo
marketNo
symbolNo
watchedNo
watchlistNo
data_as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / data_as_of / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / market / $ref
      Removed value: -"#/properties/action"
    • addedOutput schema / properties / market / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / name / $ref
      Removed value: -"#/properties/action"
    • addedOutput schema / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / symbol / $ref
      Removed value: -"#/properties/action"
    • addedOutput schema / properties / symbol / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / watchlist / items / properties / market / $ref
      Removed value: -"#/properties/action"
    • addedOutput schema / properties / watchlist / items / properties / market / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / watchlist / items / properties / name / $ref
      Removed value: -"#/properties/action"
    • addedOutput schema / properties / watchlist / items / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / watchlist / items / properties / symbol / $ref
      Removed value: -"#/properties/action"
    • addedOutput schema / properties / watchlist / items / properties / symbol / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. Changed5 schema fields changed
    • removedInput schema / properties / action / default
      Removed value: -"list"
    • changedInput schema / properties / action / description
      Previous value: -"'list' reads the watchlist; 'add' and 'remove' each need a symbol."New value: +"'add' and 'remove' each need a symbol."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "add",
      -  "remove"
      -]New value: +[
      +  "add",
      +  "remove"
      +]
    • changedInput schema / properties / symbol / description
      Previous value: -"Stock code, ticker or company name. Required for 'add' and 'remove', ignored by 'list'."New value: +"Stock code, ticker or company name. Required for 'add' and 'remove'."
    • addedInput schema / required
      Added value: +[
      +  "action"
      +]
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it defines idempotency concretely ('adding a company already on the list leaves it there, removing one that is not on the list is a no-op'), clarifies that only remove deletes an entry, and notes both actions report the resulting list size. It also bounds the blast radius by saying saved preferences change, not financial assets, which is exactly the context destructiveHint=true does not provide on its own.

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, front-loaded blocks: action, then behavior, then exclusions. Every sentence carries information, and the 'Not this tool for' header makes the routing section scannable.

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?

Two-parameter tool with 100% schema coverage, an output schema and full annotations; the description adds the mutation semantics, the idempotency contract and the conceptual boundary an agent needs. Nothing material is missing for correct invocation.

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, and the description earns an extra point by explaining what each enum value does semantically (one symbol per call, per-action idempotency) rather than just listing them. Minor gap: no guidance on ticker vs company-name resolution for the symbol field.

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 the concrete verb pair and resource ('add or remove a company from the user's watchlist') and immediately scopes it as a preferences change rather than an asset change, which separates it from the portfolio siblings.

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?

Explicitly names what this tool is NOT for and routes the agent to get_portfolio / import_portfolio, plus excludes market data use. The one gap is that get_watchlist, the sibling for reading the list, is never named even though 'Both report the resulting list size' implies a read path exists elsewhere.

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.