Skip to main content
Glama

FinBridge

by kr.gronox
OverviewDiscussionsAdmin

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
errorNo
totalNo
actionNo
marketNo
symbolNo
watchedNo
watchlistNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description clarifies that removing deletes an entry while adding is non-destructive, and that it changes saved preferences, not financial assets. This complements the destructiveHint and idempotentHint annotations.

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?

The description is somewhat repetitive in the second paragraph, restating idempotency and the exclusion of financial assets, but it remains well-organized and 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?

The description explains what the tool does, when to use it, what it does not handle, and the result behavior (reports list size). With an output schema present, this is complete enough for an agent.

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

Parameters5/5

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

Although the schema already covers the parameters, the description adds the critical conditional requirement that symbol is needed for both 'add' and 'remove', which is not fully captured by the required array. It also clarifies action semantics.

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 clearly states the tool adds or removes a company from the user's watchlist, with specific verbs and resource. It distinguishes itself from portfolio and market data tools.

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 explicitly says 'Not this tool for holdings and cash' and names the alternatives get_portfolio/import_portfolio, plus excludes market data. It also explains idempotent behavior for add/remove.

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

All FinBridge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources