Skip to main content
Glama
RohanAnandPandit

Trading212 MCP Server

create_pie

Create a diversified investment pie by assigning weights to stock tickers. Set dividend reinvestment, end date, and target value.

Instructions

Create a new pie with the specified parameters.

Args:
    name: Name of the pie
    instrument_shares: Dictionary mapping instrument tickers to their
    weights in the pie
        (e.g., {'AAPL_US_EQ': 0.5, 'MSFT_US_EQ': 0.5})
    dividend_cash_action: How dividends are handled. Defaults to REINVEST.
        Possible values: REINVEST, TO_ACCOUNT_CASH
    end_date: Optional end date for the pie in ISO 8601 format
        (e.g., '2024-12-31T23:59:59Z')
    goal: Total desired value of the pie in account currency
    icon: Optional icon identifier for the pie

Returns:
    AccountBucketInstrumentsDetailedResponse: Details of the created pie

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
instrument_sharesYes
dividend_cash_actionNo
end_dateNo
goalNo
iconNo
Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It describes the creation action but does not mention side effects, permissions needed, or what happens if the pie already exists or if instrument tickers are invalid. Minimal behavioral disclosure for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured as a docstring with a summary line followed by Args and Returns. It is somewhat verbose due to examples but well-organized and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all parameters and return type, but lacks information on error conditions, validation rules for instrument_shares, and prerequisite states. For a tool with no output schema and no annotations, more completeness is needed.

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?

Schema description coverage is 0%, so the description compensates by providing meaning for each parameter, including examples for instrument_shares and end_date, and explaining dividend_cash_action options. However, some details like constraints on goal or icon are missing.

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

Purpose5/5

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

The description clearly states 'Create a new pie with the specified parameters,' using a specific verb and resource. Among sibling tools like delete_pie, update_pie, and fetch_pies, this is the only creation tool, so it is easily distinguishable.

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 explicit guidance on when to use this tool versus alternatives such as update_pie or duplicate_pie. No prerequisites, exclusions, or context for use are provided.

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

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