Skip to main content
Glama
dacmail

indexa-capital-mcp-server

by dacmail

Get Indexa portfolio composition

indexa_get_portfolio
Read-onlyIdempotent

Retrieve your Indexa portfolio's total value, cash, holdings, cost basis, and unrealized profit/loss. Get a full breakdown by asset class and per-position detail.

Instructions

Retrieve the current portfolio of an Indexa account: total value, cash position, and the full list of instruments currently held (ISIN, name, asset class, market value, cost basis, unrealized P/L and return %).

API response shape: { "portfolio": { "total_amount", "cash_amount", "instruments_amount", "instruments_cost", "date" }, "cash_accounts": [{ "amount", "date" }], "instrument_accounts": [{ "positions": [{ "amount", "cost_amount", "price", "titles", "instrument": { "identifier"(ISIN), "name", "asset_class", "management_company_description" } }] }] }

The Markdown output includes: grand total, cost basis, total P/L and return %, breakdown by asset class with %, and per-position detail sorted by value.

Args:

  • account_number (string): Indexa account ID, from indexa_get_me

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Examples:

  • Use when: "What's my Indexa portfolio worth?"

  • Use when: "Show me what funds I'm holding"

  • Use when: "How much am I up/down on my Indexa account?"

  • Don't use for: historical returns → indexa_get_performance

  • Don't use for: transaction history → indexa_get_transactions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_numberYesIndexa account number (account_number field from indexa_get_me). Example: 'NK1NUTP1'.
response_formatNoOutput format: 'markdown' for human-readable summary or 'json' for full structured data.markdown
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds useful behavioral context by detailing the API response shape and Markdown output, plus mentions dependency on account_number from indexa_get_me. No contradictions.

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 well-structured with clear sections: purpose, API shape, markdown output, args, examples. Every sentence contributes information without redundancy. Front-loaded with key purpose.

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 no output schema, the description provides the full JSON response shape and details the Markdown summary format. It covers common use cases with examples. Comprehensive for a portfolio tool.

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?

Schema coverage is 100% and both parameters have detailed descriptions. The description adds extra value by providing an example account number and clarifying the difference between 'markdown' and 'json' output formats 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 the current portfolio composition, including total value, cash, and instrument details. It distinguishes from siblings like indexa_get_performance and indexa_get_transactions by explicitly listing what not to use it for.

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?

The description provides explicit when-to-use examples ('What's my Indexa portfolio worth?') and when-not-to-use examples with alternative tool names ('historical returns → indexa_get_performance'). This gives clear guidance.

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/dacmail/indexa-capital-mcp-server'

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