Skip to main content
Glama
KyuRish

trading212-mcp-server

update_pie

Modify an existing pie's settings, instrument allocations, or target weights. Update only the fields you provide; omitted fields remain unchanged. Requires the pie ID and name.

Instructions

Modify an existing pie's settings, instrument allocations, or target weights.
Only provided fields are updated - omitted fields remain unchanged.

Use fetch_a_pie first to see the current configuration before making changes.
The API requires providing a name even if you are not changing it.

Args:
    pie_id: Numeric ID of the pie to modify (e.g., 6894572). Get this from fetch_pies.
    name: Updated name for the pie. Required by the API even if unchanged.
    instrument_shares: New ticker-to-weight mapping, must sum to 1.0.
        Example: {'AAPL_US_EQ': 0.5, 'MSFT_US_EQ': 0.5}
    dividend_cash_action: REINVEST or TO_ACCOUNT_CASH
    end_date: Revised end date in ISO 8601 (e.g., '2029-12-31T23:59:59Z')
    goal: Revised target value in account currency (e.g., 25000.0)
    icon: Updated icon identifier

Returns:
    PieDetails: The pie after applying your changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pie_idYes
nameNo
instrument_sharesNo
dividend_cash_actionNo
end_dateNo
goalNo
iconNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsNo
instrumentsNo
Behavior4/5

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

Discloses partial update behavior ('only provided fields are updated') and API requirement for name. Does not contradict annotations. Could mention error handling but sufficient.

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?

Two paragraphs: summary, usage note, then Args list. Each sentence adds value. Front-loaded and well-organized.

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 update behavior, prerequisites, parameter details, and return type (PieDetails). Output schema exists but is referenced simply; complete for the tool's complexity.

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?

Schema description coverage is 0%, but description compensates with clear explanations for each parameter, including examples (e.g., pie_id example, instrument_shares format and sum constraint, dividend_cash_action enum).

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?

Clearly states 'Modify an existing pie's settings, instrument allocations, or target weights.' Specific verb and resource, distinguishes from sibling tools like create_pie and delete_pie.

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

Usage Guidelines4/5

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

Provides explicit guidance: 'Use fetch_a_pie first to see the current configuration before making changes.' Also notes API requires name even if unchanged. Lacks explicit when-not-to-use, but context is clear.

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