Skip to main content
Glama
mhajder

Ghostfolio MCP Server

by mhajder

get_portfolio_holdings

Read-onlyIdempotent

Retrieve current portfolio holdings, positions, allocations, and asset breakdowns for a specified time period.

Instructions

Get portfolio holdings and positions including allocations and asset breakdowns.

Retrieves current portfolio holdings including positions, allocations, and asset breakdowns for the specified time period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_rangeNoTime range for holdings data. Options: 1d, 1w, 1m, 3m, 6m, 1y, 2y, 5y, maxmax

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already signal read-only and idempotent behavior. The description adds minimal context beyond repeating the purpose, not contradicting annotations.

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?

Two sentences with no waste, but the second sentence largely restates the first, slightly redundant.

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?

With a full output schema and one well-documented parameter, the description sufficiently covers the tool's purpose and behavior for proper use.

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

Parameters3/5

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

The schema fully describes the date_range parameter with options; the description only mentions 'specified time period' without adding new 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?

The description clearly states the tool retrieves portfolio holdings and positions with allocations and asset breakdowns, distinguishing it from siblings like get_portfolio_details or get_position that focus on different aspects.

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

Usage Guidelines3/5

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

The description implies use for current holdings but provides no explicit when-to-use guidance or alternatives among the numerous sibling tools.

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