Skip to main content
Glama
RohanAnandPandit

Trading212 MCP Server

update_pie

Update an existing trading pie by renaming it and adjusting parameters including instrument weights, dividend handling, end date, goal, and icon.

Instructions

Update an existing pie with new parameters. The pie must be renamed when
updating it.

Args:
    pie_id: ID of the pie to update
    name: New name for the pie. Required when updating a pie.
    instrument_shares: Dictionary mapping instrument tickers to their new
    weights in the pie
        (e.g., {'AAPL_US_EQ': 0.5, 'MSFT_US_EQ': 0.5})
    dividend_cash_action: How dividends should be handled.
        Possible values: REINVEST, TO_ACCOUNT_CASH
    end_date: New end date for the pie in ISO 8601 format
        (e.g., '2024-12-31T23:59:59Z')
    goal: New total desired value of the pie in account currency
    icon: New icon identifier for the pie

Returns:
    AccountBucketInstrumentsDetailedResponse: Updated details of the pie

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pie_idYes
nameNo
instrument_sharesNo
dividend_cash_actionNo
end_dateNo
goalNo
iconNo
Behavior3/5

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

No annotations provided; description mentions mandatory rename and lists parameters but doesn't disclose side effects like field overwrite behavior or error conditions.

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?

Concise with a clear structure, though the list of args could be more compact.

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

Completeness4/5

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

Covers all 7 parameters with usage notes, but lacks details on return value (despite no output schema) and potential errors.

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?

With 0% schema coverage, description provides detailed parameter explanations including examples and enum values, adding significant meaning 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?

Clearly states 'Update an existing pie with new parameters', specifying verb and resource. Distinguishes from siblings 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?

Explicitly mentions mandatory rename condition, but lacks when-to-use vs alternatives or prerequisites.

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