Skip to main content
Glama

StockLens

by com.stocklens
OverviewDiscussionsAdmin

Add To Watchlist

add_to_watchlist

Add one company to the authenticated user's default StockLens portfolio as a company they follow, so its score stays readable here. Call it only when the person has asked for it or agreed to an offer. If the portfolio is already at the limit of the person's current plan, the result says so. After an add the person accepted from a get_market_summary offer, call get_market_summary again to answer their question. Does NOT execute trades, does NOT record a holding or transaction, and does NOT accept more than one ticker per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g. AAPL). Exactly one ticker per call.
exchangeNoExchange code (e.g. NASDAQ). Optional. Resolved automatically if omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYes
tickerYes
exchangeYes
plan_limitYes
company_nameNo
total_holdingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / pattern
      Previous value: -"^[A-Za-z][A-Za-z.\\-]{0,9}$"New value: +"^[A-Za-z0-9][A-Za-z0-9.\\-]{0,19}$"
  2. Changed3 schema fields changed
    • changedInput schema / properties / exchange / description
      Previous value: -"Exchange code (e.g. NASDAQ). Optional - resolved automatically if omitted."New value: +"Exchange code (e.g. NASDAQ). Optional. Resolved automatically if omitted."
    • addedInput schema / properties / exchange / enum
      Added value: +[
+  "NYSE",
+  "NASDAQ",
+  "AMEX",
+  "OTC",
+  "CBOE",
+  "TSX",
+  "TSXV",
+  "CNQ",
+  "NEO",
+  "MEX",
+  "B3",
+  "SANTIAGO",
+  "BUE",
+  "BVC",
+  "LSE",
+  "EURONEXT_PARIS",
+  "EURONEXT_AMSTERDAM",
+  "EURONEXT_BRUSSELS",
+  "EURONEXT_LISBON",
+  "EURONEXT_DUBLIN",
+  "XETRA",
+  "SIX",
+  "BME",
+  "MILAN",
+  "OSLO",
+  "OMX_STOCKHOLM",
+  "OMX_HELSINKI",
+  "OMX_COPENHAGEN",
+  "WSE",
+  "VIE",
+  "ATH",
+  "PRA",
+  "BUD",
+  "IST",
+  "ICE",
+  "RIS",
+  "TAL",
+  "MCX",
+  "TSE",
+  "HKEX",
+  "SHANGHAI",
+  "SHENZHEN",
+  "ASX",
+  "TWSE",
+  "SGX",
+  "NSE",
+  "KRX",
+  "BSE",
+  "KOE",
+  "JKT",
+  "KLS",
+  "SET",
+  "NZE",
+  "HOSE",
+  "TWO",
+  "TADAWUL",
+  "JSE",
+  "TLV",
+  "DFM",
+  "EGX",
+  "DOH",
+  "KUW"
+]
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol to add to the watchlist (e.g. AAPL). Exactly one ticker per call."New value: +"Stock ticker symbol (e.g. AAPL). Exactly one ticker per call."
  3. Changed1 schema field changed
    • changedInput schema / properties / exchange / description
      Previous value: -"Exchange code (e.g. NASDAQ). Optional — auto-resolved via StockLens autocomplete if omitted."New value: +"Exchange code (e.g. NASDAQ). Optional - resolved automatically if omitted."
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only state readOnlyHint=false and destructiveHint=false, so the description carries much of the behavioral burden. It adds valuable side-effect context: no trades, no holding/transaction recorded, one ticker per call, and plan-limit behavior. It does not mention what happens if the same ticker is added twice, but this is a minor gap given the available 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 front-loaded with the primary action, then proceeds through trigger conditions, limit behavior, follow-up workflow, and exclusions. Each sentence serves a purpose and there is no filler, though the description is somewhat dense.

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 tool is simple, the schema is rich, an output schema exists, and the description covers purpose, trigger, scope, side-effect exclusions, and post-call workflow. Nothing essential is missing for an agent to select and invoke this tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, with both ticker and exchange already documented in the input schema. The description reinforces 'exactly one ticker per call' but does not add meaning beyond the schema. A 3 is appropriate because the schema already carries the semantic load.

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 a specific verb+resource: 'Add one company to the authenticated user's default StockLens portfolio as a company they follow.' It also distinguishes itself from trading tools by explicitly saying it does NOT execute trades or record a holding/transaction, and from get_market_summary by describing the follow-up call. Purpose is unambiguous.

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 an explicit trigger condition: 'Call it only when the person has asked for it or agreed to an offer.' It also provides workflow guidance to call get_market_summary again after an accepted add. However, it does not explicitly name remove_from_watchlist as the alternative for removing a company, so sibling routing is not fully enumerated.

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

All StockLens 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