Skip to main content
Glama
kea0811
by kea0811

ig_get_working_orders

Retrieve all active working orders on IG Trading to monitor and manage open trades in forex, indices, and commodities efficiently.

Instructions

Get all working orders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that fetches all working orders from the IG API endpoint '/workingorders'
    async getWorkingOrders() {
      try {
        const response = await this.apiClient.get('/workingorders', 2);
        return response.data;
      } catch (error) {
        logger.error('Failed to get working orders:', error.message);
        throw error;
      }
    }
  • MCP tool execution handler that invokes IGService.getWorkingOrders() and returns JSON-formatted response
    case 'ig_get_working_orders':
      const orders = await igService.getWorkingOrders();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(orders, null, 2),
          },
        ],
      };
  • Tool registration in the TOOLS array, including name, description, and empty input schema
      name: 'ig_get_working_orders',
      description: 'Get all working orders',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
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. 'Get all working orders' implies a read-only operation, but it doesn't specify whether it returns active/pending orders, requires authentication, has rate limits, or includes pagination. The description is too vague to inform the agent adequately about how the tool behaves beyond basic retrieval.

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—just three words—and front-loaded with the core action. There's no wasted language, making it easy to parse quickly. Every word ('Get', 'all', 'working orders') contributes directly to understanding the tool's purpose without unnecessary elaboration.

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 a retrieval tool. It doesn't explain what 'working orders' entail (e.g., status, format) or what the return values might be. While the zero parameters simplify usage, the description fails to provide enough context for the agent to use the tool effectively without additional assumptions.

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, meaning no parameters are documented or required. The description doesn't add parameter details, which is appropriate since there are none. This aligns with the baseline for zero parameters, as the description doesn't need to compensate for missing schema information.

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 working orders' clearly states the verb ('Get') and resource ('working orders'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'ig_get_positions' or 'ig_get_watchlist', which follow similar patterns, leaving some ambiguity about scope. It's not tautological but lacks specificity about what distinguishes this retrieval operation.

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., login status), context (e.g., after creating orders), or exclusions (e.g., compared to 'ig_get_positions'). This leaves the agent with minimal direction, relying solely on the tool name in a list of siblings.

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