Skip to main content
Glama
dacmail

indexa-capital-mcp-server

by dacmail

Get Indexa management fees

indexa_get_fees
Read-onlyIdempotent

Retrieve the management fees invoiced by Indexa Capital for a specific account, including net fee, VAT, effective fee rate, and invoice PDF link. Filter by date range to get quarterly billing records.

Instructions

Retrieve the management fees charged by Indexa Capital on an account. Indexa bills quarterly, and this endpoint returns one record per quarter, including the asset base used, the net fee, VAT, the effective fee rate, and a link to the invoice PDF.

Args:

  • account_number (string): Indexa account ID

  • date_from (string, optional): Filter to quarters that end on or after this date (YYYY-MM-DD)

  • date_to (string, optional): Filter to quarters that start on or before this date (YYYY-MM-DD)

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

Returns: For JSON format, an array of fee records: [ { "account_number": string, "date_from": "YYYY-MM-DD", // start of the billing quarter "date_to": "YYYY-MM-DD", // end of the billing quarter "fees": number, // net management fee in EUR "vat": number, // VAT applied in EUR "amount": number, // asset base used "average_fee": number, // effective fee rate (e.g. 1.95 = 1.95 bps avg) "document": { // invoice PDF metadata "showName": string, "show_name": string, "created_at": "YYYY-MM-DD HH:mm:ss" } } ]

The Markdown format computes total fees and total VAT for the filtered range.

Examples:

  • Use when: "How much did Indexa charge me in fees last year?"

  • Use when: "What's my effective fee rate on my pension account?"

  • Use when: "List all fee invoices since 2023"

Error handling:

  • 404: account not found or no fees yet (e.g. very recently opened).

  • 401/403: token invalid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_numberYesIndexa account number (account_number field from indexa_get_me). Example: 'NK1NUTP1'.
date_fromNoDate in YYYY-MM-DD format. Example: '2024-01-15'.
date_toNoDate in YYYY-MM-DD format. Example: '2024-01-15'.
response_formatNoOutput format: 'markdown' for human-readable summary or 'json' for full structured data.markdown
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), description details that it returns one record per quarter, includes asset base, net fee, VAT, effective fee rate, and invoice PDF link. Also explains error handling (404, 401/403) and date filtering logic.

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?

Well-structured with sections for description, args, returns, examples, and error handling. Somewhat verbose but all sentences contribute value; front-loading is effective.

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?

Despite no output schema, description fully documents return fields for JSON format, explains Markdown summary, and covers filtering behavior and error codes. Complete for an agent to use without ambiguity.

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% with good descriptions, but the description adds semantics like 'quarters that end on or after this date' for date_from and 'quarters that start on or before this date' for date_to, plus examples for account_number and response_format.

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?

Description clearly states 'Retrieve the management fees charged by Indexa Capital on an account' with specific verb and resource. Distinguishes from sibling tools like indexa_get_transactions or indexa_get_performance by focusing exclusively on fees.

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?

Provides concrete examples under 'Use when:' (e.g., 'How much did Indexa charge me in fees last year?') and explains the quarterly billing context. Does not explicitly exclude other tools but the usage is well implied.

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