Skip to main content
Glama
Sign In
EDGAR Alert MCP Server

EDGAR Alert MCP Server

by ikop32-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add ticker to watchlist

edgaralert_add_ticker_to_list

Add a stock ticker to your ticker list or watchlist. Obtain list IDs with the get ticker lists tool, then supply the list ID and ticker symbol.

Instructions

Adds a stock ticker to one of the user's ticker lists (watchlists). Use edgaralert_get_ticker_lists first to find the correct listId. Plan limits apply: FREE/STARTER plans are capped at 10 tickers total across all lists. Returns the created ticker list item on success.

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": {
      "listId": "<listId>",
      "ticker": "<ticker>"
    },
    "name": "edgaralert_add_ticker_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe ID of the ticker list to add to. Get list IDs from edgaralert_get_ticker_lists.
tickerYesStock ticker to add, e.g. AAPL. Will be uppercased automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.7/5.0
Behavior4/5

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

Discloses plan limits (FREE/STARTER capped at 10 tickers) and return value (created item). Annotations already indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false), so description adds useful context without contradiction.

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?

Two succinct sentences that front-load the main action and include essential usage guidance without extraneous text.

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?

Given simple tool (2 required params, no output schema), description covers prerequisite, plan limits, return behavior, and parameter nuances. Provides a complete picture 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 already has 100% coverage with descriptions for both parameters. Description adds extra context: for listId, references prerequisite tool; for ticker, notes uppercasing. This adds value beyond schema.

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?

Clearly states 'Adds a stock ticker to one of the user's ticker lists (watchlists).' This specifies the verb (adds), resource (ticker to list), differentiates from siblings like get_ticker_lists and remove_ticker_from_list.

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?

Explicitly instructs to use edgaralert_get_ticker_lists first to find the correct listId, and mentions plan limits. Provides clear when-to-use and constraints.

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

Deploy Server

Other Tools