Skip to main content
Glama
kea0811
by kea0811

ig_logout

Log out from an IG Trading account securely via the IG Trading MCP server. Use this tool to close active sessions and manage account access.

Instructions

Logout from IG Trading account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for ig_logout that delegates to IGService.logout() and formats the response.
    case 'ig_logout':
      await igService.logout();
      return {
        content: [
          {
            type: 'text',
            text: 'Successfully logged out',
          },
        ],
      };
  • Tool registration in TOOLS array, including name, description, and empty input schema.
    {
      name: 'ig_logout',
      description: 'Logout from IG Trading account',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • IGService.logout method: core implementation that calls IG API DELETE /session and clears session tokens.
    async logout() {
      try {
        const response = await this.apiClient.delete('/session');
        config.clearSessionTokens();
        logger.info('Logout successful');
        return response;
      } catch (error) {
        logger.error('Logout failed:', 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 only states the action without behavioral details. It doesn't disclose what 'logout' entails (e.g., session termination, token invalidation), side effects, authentication requirements, or error handling, leaving significant gaps.

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, clear sentence with zero wasted words, front-loading the essential action and target. It's appropriately sized for a simple tool with no parameters, making it highly efficient.

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 tool that performs a state-changing operation (logout) with no annotations or output schema, the description is incomplete. It lacks details on behavior, side effects, success indicators, or error scenarios, which are critical for an agent to use it correctly in context.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, aligning with the schema, earning a baseline score above minimum viable.

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 ('Logout') and target resource ('IG Trading account'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ig_login' beyond the obvious action contrast, missing explicit comparison.

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 or prerequisites. While the context implies it should be used after authentication (given 'ig_login' exists), the description lacks explicit instructions about timing, dependencies, or error conditions.

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