Skip to main content
Glama
KyuRish

trading212-mcp-server

create_pie

Build an investment portfolio pie by assigning target weights to ticker symbols. Fund the pie to execute purchases. Weights must sum to 100%.

Instructions

Create a new investment pie with the given instruments and target weights.
This creates a real pie in your account - instruments will be purchased
when you fund the pie.

Use search_instrument to find valid ticker symbols before creating. Weights
must sum to 1.0 (100%). See also: duplicate_pie to clone an existing pie.

Args:
    name: Display name for the pie (e.g., 'Tech Growth')
    instrument_shares: Mapping of ticker to target weight, must sum to 1.0.
        Example: {'AAPL_US_EQ': 0.5, 'MSFT_US_EQ': 0.3, 'NVDA_US_EQ': 0.2}
    dividend_cash_action: REINVEST (buy more shares) or TO_ACCOUNT_CASH (withdraw to cash).
        Defaults to REINVEST if not specified.
    end_date: Optional target date in ISO 8601 (e.g., '2029-12-31T23:59:59Z')
    goal: Optional target value in account currency (e.g., 20000.0)
    icon: Optional pie icon identifier (e.g., 'Coins', 'Education')

Returns:
    PieDetails: Full details of the newly created pie

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
instrument_sharesYes
dividend_cash_actionNo
end_dateNo
goalNo
iconNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsNo
instrumentsNo
Behavior5/5

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

Discloses that creation is real and triggers purchase upon funding, beyond the annotations which only indicate non-read-only, non-destructive, non-idempotent. Adds meaningful context without contradiction.

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?

Concise yet informative: single-sentence purpose, followed by usage guidelines, then structured parameter explanations. No fluff, every sentence earns its place.

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

Completeness5/5

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

Covers creation process, prerequisites, constraints, defaults, and return type. Given the complexity (6 params, nested objects), the description is fully complete and agent-ready.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage, the description explains each parameter with examples, defaults, and constraints (e.g., weights must sum to 1.0, dividend_cash_action default). Adds significant value beyond the schema.

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 the tool creates a new investment pie, with specifics that it's a real creation and instruments are purchased on funding. It distinguishes from siblings like duplicate_pie, delete_pie, update_pie.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises using search_instrument first, states weight constraint (sum to 1.0), and references duplicate_pie as an alternative for cloning. Provides clear when-to-use and when-not-to-use guidance.

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

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