Skip to main content
Glama

StockLens

by com.stocklens
OverviewDiscussionsAdmin

Get Portfolio Insights

get_portfolio_insights
Read-onlyIdempotent

Retrieve StockLens analysis summaries for the authenticated user's watchlist. Returns available composite scores and grades for watchlisted stocks; either value may be absent when no completed score exists. Returns the full watchlist up to the plan's capacity — Free tracks up to 10 stocks; Pro and Max plans track an unlimited number. Use this to give users an overview of their portfolio's analytical health. Does NOT accept a ticker or filter arguments and does NOT rank or screen stocks outside the user's own watchlist — call discover_stocks for a market-wide ranked or filtered list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYes
watchlistYes
tier_limitedYes
total_holdingsYes
aggregate_signalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / scope
      Added value: +{
+  "enum": [
+    "user_watchlist"
+  ],
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "watchlist",
-  "total_holdings",
-  "tier_limited"
-]New value: +[
+  "watchlist",
+  "total_holdings",
+  "tier_limited",
+  "scope"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond that: plan-based capacity limits (Free up to 10 stocks, Pro/Max unlimited) and the fact that scores/grades may be absent when no completed score exists. These are useful behavioral details not in the annotations.

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?

The description is two sentences with zero wasted words. It front-loads the core purpose, then packs in capacity limits, missing-data behavior, and a sibling reference, all in a compact, scannable format.

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?

For a tool with no parameters, clear read-only annotations, and an output schema (which presumably describes the returned data), the description fully covers what it returns, plan constraints, and exclusions, leaving no gaps for an agent to call it correctly.

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?

The tool has zero parameters, so per guidelines the baseline is 4. The description adds no parameter-specific info (none needed) and correctly states it accepts no ticker/filter arguments, which clarifies the lack of parameters.

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 states a specific verb ('Retrieve'), resource ('StockLens analysis summaries for the authenticated user's watchlist'), and clearly distinguishes itself from siblings by explicitly excluding ticker/filter arguments and market-wide ranking, pointing to discover_stocks for that. This makes the tool's unique purpose unmistakable.

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 when to use it ('to give users an overview of their portfolio's analytical health') and when not to (does NOT rank/screen outside watchlist) and names the alternative (discover_stocks). This is exactly the when/when-not guidance an agent needs.

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