Skip to main content
Glama
kinmeic

Stock MCP Server

by kinmeic

watch_remove

Remove a stock from your watchlist by specifying its code and market to manage your investment tracking.

Instructions

删除观察股票

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes股票代码
marketYes市场

Implementation Reference

  • Tool handler that processes watch_remove requests - validates input using RemoveWatchSchema, calls watch.removeWatch(), and returns success/failure response
    if (name === 'watch_remove') {
      const params = RemoveWatchSchema.parse(args);
      const success = watch.removeWatch(params.code, params.market as Market);
      if (!success) {
        throw new Error('Watch item not found');
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({ success: true }, null, 2),
          },
        ],
      };
    }
  • Core implementation of removeWatch function - loads watch list, finds item by code and market, removes it, saves updated list, and returns success status
    export function removeWatch(code: string, market: Market): boolean {
      const watchList = loadWatchList();
      const index = watchList.findIndex(item => item.code === code && item.market === market);
    
      if (index === -1) {
        return false;
      }
    
      watchList.splice(index, 1);
      saveWatchList(watchList);
      return true;
    }
  • Zod validation schema for watch_remove tool parameters - requires code (string) and market (enum: sh, sz, hk, us)
    const RemoveWatchSchema = z.object({
      code: z.string().describe('股票代码'),
      market: z.enum(['sh', 'sz', 'hk', 'us']).describe('市场'),
    });
  • src/index.ts:232-243 (registration)
    Tool registration in MCP server - defines watch_remove tool with name, description, and JSON input schema for the tools list endpoint
    {
      name: 'watch_remove',
      description: '删除观察股票',
      inputSchema: {
        type: 'object',
        properties: {
          code: { type: 'string', description: '股票代码' },
          market: { type: 'string', enum: ['sh', 'sz', 'hk', 'us'], description: '市场' },
        },
        required: ['code', 'market'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('删除' - delete/remove). It doesn't disclose behavioral traits like whether removal is permanent, requires specific permissions, has side effects, returns confirmation, or handles errors. For a mutation tool with zero annotation coverage, this is insufficient.

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 a single, efficient phrase ('删除观察股票') with zero wasted words. It's appropriately sized for a simple removal operation and immediately states the core purpose.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after removal, whether confirmation is returned, error conditions, or relationships to other watch operations. Given the tool's destructive nature and lack of structured safety hints, more context is needed.

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%, with both parameters clearly documented in the schema (code=stock code, market=market with enum values). The description adds no additional parameter meaning beyond what the schema provides, meeting the baseline for high schema coverage.

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 '删除观察股票' (remove watch stock) clearly states the action (remove) and target resource (watch stock). It distinguishes from sibling tools like watch_add (add) and watch_list (list), but doesn't specify what constitutes a 'watch stock' versus other stock-related resources.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., stock must be in watchlist first), when-not scenarios, or relationships to siblings like watch_list (to check existing watches) or watch_add (to add watches).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kinmeic/stock-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server