Skip to main content
Glama
mhajder

Ghostfolio MCP Server

by mhajder

upsert_asset_profile

Idempotent

Create or update an asset profile by posting an empty record and patching metadata. Idempotent and error-tolerant.

Instructions

Create-or-update an asset profile.

POSTs an empty profile-data record (idempotent — Ghostfolio returns HTTP 500 on both duplicate-create and some first-time-create paths while still persisting the record, so this tolerates 500). Then PATCHes metadata (name, currency, asset class, optional sub-class). PATCH is the source of truth — if the profile doesn't exist after the POST, PATCH will surface a 404. Calling twice with the same input yields the same end state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable name for the asset
symbolYesSymbol/ticker of the asset. Permanent — renaming orphans associated activities and market data
currencyYesCurrency code of the asset (e.g., 'USD', 'CHF', 'EUR')
asset_classYesAsset class: 'EQUITY', 'FIXED_INCOME', 'REAL_ESTATE', 'COMMODITY', 'LIQUIDITY' (cash), or 'ALTERNATIVE_INVESTMENT'. Note: Ghostfolio's enum does not include 'CASH' — use 'LIQUIDITY'
data_sourceYesData source for the symbol. Typically 'MANUAL' — Ghostfolio rejects profile-data writes for auto-fetched sources
asset_sub_classNoOptional asset sub-class (e.g., 'MUTUALFUND', 'CASH', 'ETF')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Goes beyond annotations by detailing idempotency, tolerance of HTTP 500, and that PATCH is source of truth. No contradiction with annotations.

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?

Every sentence is essential and informative. No wasted words; clear and efficient.

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 behavior, errors, idempotency, and parameter details. Output schema exists, further reducing need for return value description. Complete for a complex upsert tool.

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?

Adds critical context beyond schema: symbol permanence, asset_class enum note, data_source typical value. Schema coverage is 100%, but description enhances understanding.

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 'Create-or-update an asset profile' with specific fields (name, currency, asset class, sub-class). Distinguishes from sibling tools like get_asset_profile and delete_asset_profile.

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?

Describes two-step process (POST then PATCH), idempotent behavior, and error handling. Does not explicitly state 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/mhajder/ghostfolio-mcp'

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