Skip to main content
Glama
kea0811
by kea0811

ig_get_watchlist

Retrieve detailed information about a specific trading watchlist using the IG Trading API. Ideal for managing and analyzing forex, indices, and commodities data within the IG Trading MCP server.

Instructions

Get details of a specific watchlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchlistIdYesWatchlist ID

Implementation Reference

  • Tool registration in TOOLS array, including name, description, and input schema requiring watchlistId.
      name: 'ig_get_watchlist',
      description: 'Get details of a specific watchlist',
      inputSchema: {
        type: 'object',
        properties: {
          watchlistId: {
            type: 'string',
            description: 'Watchlist ID',
          },
        },
        required: ['watchlistId'],
      },
    },
  • MCP server request handler for ig_get_watchlist tool, delegates to IGService.getWatchlist and returns JSON response.
    case 'ig_get_watchlist':
      const watchlist = await igService.getWatchlist(args.watchlistId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(watchlist, null, 2),
          },
        ],
      };
  • Core implementation of getWatchlist method in IGService class, performs API call to fetch specific watchlist data.
    async getWatchlist(watchlistId) {
      try {
        const response = await this.apiClient.get(`/watchlists/${watchlistId}`);
        return response.data;
      } catch (error) {
        logger.error(`Failed to get watchlist ${watchlistId}:`, error.message);
        throw error;
      }
    }
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 offers minimal behavioral insight. It implies a read-only operation ('Get'), but doesn't disclose authentication needs, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this leaves critical behavioral traits unspecified, though it doesn't contradict any 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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes to understanding the 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?

Given the lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what 'details' include (e.g., watchlist name, contents, metadata), potential errors, or authentication requirements. For a tool with no structured behavioral or output information, the description should provide more context to compensate, but it remains minimal.

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 the parameter 'watchlistId' clearly documented in the schema. The description adds no additional meaning beyond implying the parameter identifies the watchlist to retrieve. Since the schema fully describes the single parameter, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 clearly states the action ('Get details') and target resource ('a specific watchlist'), making the purpose immediately understandable. It distinguishes from the sibling 'ig_get_watchlists' by specifying retrieval of a single watchlist rather than a list. However, it doesn't explicitly mention what 'details' include or contrast with other sibling tools that might also retrieve watchlist information.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a watchlist ID), contrast with 'ig_get_watchlists' for listing all watchlists, or specify use cases like retrieving metadata for editing or viewing. The agent must infer usage from the name and context alone.

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

Related 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/kea0811/ig-trading-mcp'

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