Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_dividends

Retrieve dividend payment history for specific stocks with pagination support to track investment income over time.

Instructions

Get dividend payment history with pagination support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor for fetching next page
limitNoMaximum number of results to return
tickerNoFilter by ticker symbol

Implementation Reference

  • MCP tool handler for 'get_dividends' which calls the client method.
    case 'get_dividends': {
      const { cursor, limit, ticker } = PaginatedWithTickerInputSchema.parse(args);
      const dividends = await client.getDividends({ cursor, limit, ticker });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(dividends, null, 2),
          },
        ],
      };
    }
  • Actual client implementation for fetching dividend history.
    async getDividends(params?: {
      cursor?: number;
      limit?: number;
      ticker?: string;
    }): Promise<{ items: Dividend[]; nextPagePath?: string }> {
      const queryParams = new URLSearchParams();
      if (params?.cursor) queryParams.append('cursor', params.cursor.toString());
      if (params?.limit) queryParams.append('limit', params.limit.toString());
      if (params?.ticker) queryParams.append('ticker', params.ticker);
    
      const endpoint = `/equity/history/dividends${queryParams.toString() ? `?${queryParams.toString()}` : ''}`;
      const response = await this.request<{ items: unknown[]; nextPagePath?: string }>(endpoint);
    
      return {
        items: z.array(DividendSchema).parse(response.items),
        nextPagePath: response.nextPagePath,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'pagination support' which is useful, but doesn't describe authentication requirements, rate limits, error conditions, or what format the dividend history returns. For a data retrieval tool with no annotation coverage, this leaves significant behavioral aspects undocumented.

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 at just 7 words. It's front-loaded with the core purpose and includes one important behavioral feature (pagination support). Every word earns its place with no redundancy or 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?

For a data retrieval tool with 3 parameters and no output schema, the description is insufficient. It doesn't explain what the dividend history includes (amounts, dates, frequency), doesn't mention authentication requirements, and provides no context about data freshness or limitations. With no annotations and no output schema, more completeness is needed.

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%, so all parameters are documented in the schema. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain how pagination works with the cursor parameter, typical limit values, or ticker symbol format requirements. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose: 'Get dividend payment history' specifies the verb (get) and resource (dividend payment history). It distinguishes from siblings like get_account_cash or get_transactions by focusing specifically on dividends. However, it doesn't explicitly differentiate from get_position or get_portfolio which might also contain dividend 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 mentions 'pagination support' which is a feature but doesn't indicate when this tool is preferred over other data retrieval tools like get_transactions or get_portfolio. There's no mention of prerequisites, constraints, or typical use cases.

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

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/enderekici/trading212-mcp'

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