Skip to main content
Glama
kea0811
by kea0811

ig_create_watchlist

Create a custom watchlist on IG Trading by specifying a name and adding initial market instruments (epics) for tracking forex, indices, and commodities.

Instructions

Create a new watchlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
epicsNoInitial epics to add
nameYesWatchlist name

Implementation Reference

  • Core handler function in IGService that creates a watchlist by posting to the IG API /watchlists endpoint with the provided name and initial epics.
    async createWatchlist(name, epics = []) {
      try {
        const response = await this.apiClient.post('/watchlists', { name, epics });
        return response.data;
      } catch (error) {
        logger.error('Failed to create watchlist:', error.message);
        throw error;
      }
    }
  • MCP tool handler in the switch statement that invokes the IGService.createWatchlist method with parsed arguments and formats the response as MCP content.
    case 'ig_create_watchlist':
      const newWatchlist = await igService.createWatchlist(args.name, args.epics || []);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(newWatchlist, null, 2),
          },
        ],
      };
  • Tool registration in the TOOLS array, including name, description, and input schema for listing in MCP tool discovery.
    {
      name: 'ig_create_watchlist',
      description: 'Create a new watchlist',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Watchlist name',
          },
          epics: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Initial epics to add',
            default: [],
          },
        },
        required: ['name'],
      },
    },
  • Input schema definition for the ig_create_watchlist tool, specifying parameters name (required string) and epics (optional array of strings).
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Watchlist name',
        },
        epics: {
          type: 'array',
          items: {
            type: 'string',
          },
          description: 'Initial epics to add',
          default: [],
        },
      },
      required: ['name'],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Create a new watchlist', implying a write operation, but does not disclose any behavioral traits such as required permissions, whether the operation is idempotent, rate limits, or what happens on success/failure. The description is minimal and fails to provide necessary context for safe and effective use.

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 a single sentence 'Create a new watchlist'. It is front-loaded and wastes no words, making it easy to parse. However, this conciseness comes at the cost of completeness, as noted in other dimensions.

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 complexity of a creation tool in a trading platform, with no annotations and no output schema, the description is incomplete. It does not explain what a watchlist is, its purpose, expected return values, or error conditions. The minimal description fails to provide sufficient context for an AI agent to use the tool effectively, especially compared to more detailed sibling tools.

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?

The input schema has 100% description coverage, with clear documentation for 'name' and 'epics' parameters. The description does not add any semantic meaning beyond what the schema provides, as it mentions no parameters. According to the rules, with high schema coverage (>80%), the baseline score is 3, even without parameter info in the description.

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

Purpose2/5

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

The description 'Create a new watchlist' is a tautology that merely restates the tool name 'ig_create_watchlist'. It specifies the verb 'create' and resource 'watchlist', but lacks any detail about what a watchlist is or its purpose in the context of the IG trading platform. It does not differentiate from sibling tools like 'ig_get_watchlists' or 'ig_get_watchlist', which are related but distinct operations.

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

Usage Guidelines1/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 does not mention prerequisites (e.g., authentication via 'ig_login'), exclusions, or comparisons to sibling tools such as 'ig_add_to_watchlist' for modifying existing watchlists. Without any context, an AI agent cannot determine appropriate usage scenarios.

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