Skip to main content
Glama
dacmail

indexa-capital-mcp-server

by dacmail

Get Indexa account details

indexa_get_account
Read-onlyIdempotent

Retrieve account details including product type, risk profile, holders, status, funding state, and currency for an Indexa account given its account number.

Instructions

Retrieve static information about a single Indexa account: product type (cartera de fondos / plan de pensiones), risk profile (1-10), holders, account status, funding state and currency.

This tool does NOT return the current portfolio value, holdings, or performance — for those use indexa_get_portfolio and indexa_get_performance.

Args:

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

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

Returns: For JSON format, the raw response from GET /accounts/{account_number}: { "account_number": string, "account_type": "personal" | "company" | "minor", "type": "mutual" | "pension", "currency": string, // typically "EUR" "status": string, // "active", "pending-contract", etc. "funding": "total" | "partial" | "no", "profile": { "selected_risk": 1-10, // user-selected risk level "risk": { "tolerance": 1-10, // questionnaire-derived "capacity": 1-10, "total": 1-10 // = min(tolerance, capacity) }, "is_outdated": boolean, "needs_to_be_updated": boolean }, "holders": [...], // titulares con nombre y DNI "platform_code": string }

Examples:

  • Use when: "What's my risk profile on account NK1NUTP1?"

  • Use when: "Is my pension account active?"

  • Don't use when: The user wants the current portfolio value (use indexa_get_portfolio) or returns (use indexa_get_performance).

Error handling:

  • 404: account_number does not exist or you don't have access to it.

  • 401/403: token invalid or revoked.

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 and idempotentHint. The description adds value by specifying the static nature, listing return fields, and including error handling (404, 401/403), which are beyond the 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?

The description is well-structured with clear sections (purpose, exclusions, args, returns, examples, error handling). Each sentence adds value, and the main purpose is front-loaded.

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 having no output schema, the description provides a detailed JSON response structure and covers error scenarios. With only 2 parameters and good annotations, the description is complete for effective tool usage.

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% with good descriptions, but the description further clarifies parameter usage (e.g., account_number origin, default response_format) and provides a full JSON response example that enriches 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?

The description starts with a clear verb ('Retrieve') and resource ('static information about a single Indexa account'), lists specific fields, and explicitly distinguishes from sibling tools by stating what it does not return.

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 states when not to use (for portfolio value or performance) and names alternative tools (indexa_get_portfolio, indexa_get_performance). Also provides 'use when' examples.

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