Skip to main content
Glama
mhajder

Ghostfolio MCP Server

by mhajder

Update Account

update_account
Idempotent

Update an existing account's name, currency, platform, comment, or balance. Provide only the fields you want to change; missing fields are retained from current state.

Instructions

Update settings or details of an existing account.

Ghostfolio's update endpoint replaces the whole account record, so name, currency and platform_id are required on every request even when they are not changing. Any left unset here are backfilled from the account's current state with a GET before the PUT, so you only need to pass the fields you actually want to change.

Setting balance here applies it as today's entry in the account's balance history (the same series get_account_balances returns and get_portfolio_holdings derives its cash figure from) - it is not a separate stale field. Use create_account_balance to set the balance for a specific past date instead of today.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional new name of the account
balanceNoOptional new balance for the account
commentNoOptional new comment or note for the account
currencyNoOptional new currency code for the account (e.g., 'USD', 'EUR')
account_idYesAccount ID to update
platform_idNoOptional new platform ID for the account

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.6.2
    • removedInput schema / properties / is_excluded
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "boolean"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Optional boolean to exclude/include in portfolio calculations"
      -}
  2. First observedv1.5.0

TDQS

A5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the endpoint replaces the whole record, that unset fields are backfilled via a GET before PUT, and that balance is applied as today's entry in the history series. This is valuable behavioral context not present in readOnlyHint/idempotentHint/destructiveHint.

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 front-loaded with the core purpose, then adds critical behavioral details in a logical order. Every sentence contributes meaningful information, and there is no redundant restatement of the schema.

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?

Given the output schema exists, return values need no explanation. The description covers the tricky replacement semantics, parameter backfilling, balance history behavior, and the key sibling alternative, making the tool fully usable without further inference.

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 coverage is 100%, but the description still adds significant meaning, especially for `balance` (today's history entry, not a stale field) and for `name`/`currency`/`platform_id` (required by the underlying endpoint but backfilled by the wrapper). This resolves ambiguity the schema alone could not.

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?

States a clear verb and resource: updating settings or details of an existing account. The distinction from create/delete/transfer siblings is apparent from the wording 'existing account' and 'settings or details'.

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 explains when to use this tool and provides an alternative: 'Use create_account_balance to set the balance for a specific past date instead of today.' It also clarifies that only changed fields need to be passed, which is essential practical guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/mhajder/ghostfolio-mcp'

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