Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Create a watchlist

watchlist_create

Create an empty Stockbit watchlist with a specified name to organize stocks for tracking and monitoring.

Instructions

Creates an empty watchlist with the given name.

Endpoint: POST exodus /watchlist.

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": {
      "name": "<name>"
    },
    "name": "watchlist_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new watchlist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the created watchlist is empty — plus an endpoint path of limited agent value. It says nothing about duplicate-name behavior or what identifier comes back for later calls.

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 core sentence is front-loaded and efficient. The trailing "Endpoint: POST exodus /watchlist" line is mostly implementation trivia for an agent but is short and not disruptive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what the call returns (e.g., the new watchlist identifier) since that is what makes follow-up calls possible. It also omits any note on whether names must be unique. Adequate for a one-parameter create, but leaves a real gap for chaining.

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% for the single parameter (name, 1-60 chars), so the schema carries the constraints. The description only restates "with the given name" and adds no format, naming convention, or uniqueness semantics beyond the schema.

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?

States a specific verb and resource ("Creates an empty watchlist") with a scope qualifier — "empty" — that signals this does not add symbols. That qualifier distinguishes it from the watchlist_add sibling, though no sibling is named 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 must infer that after creating an empty watchlist it should follow up with watchlist_add. There is no statement about when to prefer this over other watchlist operations, no prerequisites, and no mention of name collisions or limits.

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