Skip to main content
Glama
Sign In
EDGAR Alert MCP Server

EDGAR Alert MCP Server

by ikop32-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove ticker from watchlist

edgaralert_remove_ticker_from_list
DestructiveIdempotent

Remove a stock ticker from one of your ticker lists using the list ID and ticker symbol. Success returns no content; an error if ticker not in list.

Instructions

Removes a stock ticker from one of the user's ticker lists (watchlists). Use edgaralert_get_ticker_lists first to find the correct listId. Returns no content on success (204). Returns an error if the ticker is not found in the list.

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_remove_ticker_from_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe ID of the ticker list to remove from. Get list IDs from edgaralert_get_ticker_lists.
tickerYesStock ticker to remove, e.g. AAPL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate destructive and idempotent hints; description adds HTTP 204 success code and error condition for missing ticker, providing behavioral detail beyond 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?

Two concise sentences with no unnecessary words, efficiently front-loading the action and essential usage guidance.

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 two simple parameters, no output schema, and annotations covering safety, the description fully covers purpose, prerequisite, return code, and error handling.

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 coverage is 100%, and description adds value by referencing a sibling tool for listId and giving a ticker example (e.g., AAPL), enriching parameter understanding.

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 the action 'removes a stock ticker' from a watchlist, distinguishing from sibling 'add_ticker_to_list' and specifying the resource.

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?

Explicitly advises to use 'edgaralert_get_ticker_lists' first to obtain listId, and notes error cases. Lacks explicit when-not scenarios but provides sufficient context.

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