Skip to main content
Glama
kea0811
by kea0811

ig_get_watchlists

Retrieve all watchlists for forex, indices, and commodities trading via the IG Trading API. Simplify market data analysis and portfolio management by accessing curated lists of instruments.

Instructions

Get all watchlists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the ig_get_watchlists tool. Fetches all watchlists from the IG API endpoint '/watchlists' and returns the response data.
    async getWatchlists() {
      try {
        const response = await this.apiClient.get('/watchlists');
        return response.data;
      } catch (error) {
        logger.error('Failed to get watchlists:', error.message);
        throw error;
      }
    }
  • MCP server tool handler for ig_get_watchlists. Calls IGService.getWatchlists() and formats the response as MCP content.
    case 'ig_get_watchlists':
      const watchlists = await igService.getWatchlists();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(watchlists, null, 2),
          },
        ],
      };
  • Input schema and tool metadata definition for ig_get_watchlists, used in tool listing and validation.
    {
      name: 'ig_get_watchlists',
      description: 'Get all watchlists',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registration of tool list handler that exposes the ig_get_watchlists tool via the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: TOOLS,
      };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Get all watchlists') without mentioning permissions, rate limits, pagination, or response format. This is inadequate for a tool that likely involves data retrieval, as critical behavioral traits are missing.

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 extremely concise with 'Get all watchlists', a single phrase that directly states the purpose without any waste. It's front-loaded and appropriately sized for a simple tool, earning full marks for efficiency.

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. It doesn't explain what 'all watchlists' entails (e.g., user-specific, system-wide), how results are returned, or any error conditions. For a retrieval tool with no structured support, this leaves significant gaps in understanding.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but since there are no parameters, this is acceptable, and the baseline score of 4 reflects that the description doesn't need to compensate for any gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all watchlists' states a clear verb ('Get') and resource ('watchlists'), but it's vague about scope and lacks differentiation from sibling tools like 'ig_get_watchlist' (singular). It doesn't specify if this retrieves user-specific, system-wide, or all accessible watchlists, which reduces clarity.

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 on when to use this tool versus alternatives. For example, it doesn't explain when to choose 'ig_get_watchlists' over 'ig_get_watchlist' (singular) or other sibling tools like 'ig_get_accounts', leaving the agent without context for selection.

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