Skip to main content
Glama

My watchlists

my_watchlists
Read-onlyIdempotent

The signed-in person's StockMap watchlists: each list's stocks with the model's published call on each (the same call every reader sees), the calls that changed last night first. Each answer carries the not-advice line and the run date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_watchlists"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
runYes
urlNohttps://stockmap.io/watchlist
listsYes
not_adviceNoThe model's track-recorded read, not financial advice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the description's job is to add operational context — and it does: results are scoped to the signed-in identity, sorted with overnight changes first, and always carry a disclaimer line and run date. It does not cover the empty-watchlist case or pagination/size limits.

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?

Two sentences, front-loaded with the resource and its contents, no filler. The parenthetical '(the same call every reader sees)' is slightly wordy but earns its place by preempting an assumption that calls are personalized.

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 zero-parameter read tool with an output schema and full annotation coverage, the description supplies the remaining non-obvious facts: identity scoping, ordering, and the presence of a disclaimer/run date in every response. Nothing an agent needs in order to call it correctly is missing.

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 takes zero parameters, so there is nothing for the description to disambiguate at the parameter level; this is the baseline case. The description instead spends its words on payload shape, which is appropriate.

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?

The description names a specific resource (the signed-in person's StockMap watchlists) and states precisely what each entry contains (stocks plus the model's published call). It implicitly separates itself from the write-side siblings watch/unwatch by framing this as a retrieval, but never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the read path for a watchlist, while watch/unwatch mutate it. There is no statement of when to prefer this over last_night or stock_call, even though the 'changed last night first' ordering brushes against last_night's territory without disambiguating.

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.

Resources