Skip to main content
Glama
FinamWeb

Finam MCP Server

by FinamWeb

account_get_info

Retrieve account details including status, available funds, daily profit, open positions, and portfolio type from the Finam trading platform.

Instructions

Получение информации по конкретному счету (статус и тип аккаунта, доступные средства, дневная прибыль, открытые позиции (количество, средняя цена, прибыль/убыток), тип портфеля)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cashNo
typeYes
equityNo
statusYes
positionsNo
account_idYes
open_account_dateYes
unrealized_profitNo
first_non_trade_dateYes

Implementation Reference

  • MCP tool handler for account_get_info (function named get_info under account prefix). Fetches account details using Finam client.
    @account_mcp.tool(tags={"account"})
    async def get_info() -> GetAccountResponse:
        """Получение информации по конкретному счету (статус и тип аккаунта, доступные средства, дневная прибыль, открытые позиции (количество, средняя цена, прибыль/убыток), тип портфеля)"""
        return await get_finam_client().get_account_info()
  • Pydantic schema for the account information response.
    class GetAccountResponse(BaseModel):
        account_id: str
        type: str
        status: str
        positions: list[Position] = Field(default_factory=list)
        cash: list[FinamMoney] = Field(default_factory=list)
        open_account_date: AwareDatetime
        first_non_trade_date: AwareDatetime
        equity: FinamDecimal | None = None
        unrealized_profit: FinamDecimal | None = None
  • src/main.py:11-15 (registration)
    Registers the account_mcp server with 'account' prefix, prefixing tool names (e.g., get_info becomes account_get_info).
    finam_mcp = FastMCP("FinamMCP", include_tags=settings.INCLUDE_SERVERS)
    finam_mcp.mount(account_mcp, prefix="account")
    finam_mcp.mount(market_data_mcp, prefix="market_data")
    finam_mcp.mount(assets_mcp, prefix="assets")
    finam_mcp.mount(order_mcp, prefix="order")
  • Helper method in FinamClient that implements the core logic to retrieve account info from the API.
    async def get_account_info(self):
        account_client = self.client.account
        return GetAccountResponse(**await self._exec_request(account_client, BaseClient.RequestMethod.GET,
                                                             f"{account_client._url}/{self.account_id}"))
  • Utility function to retrieve the FinamClient instance from MCP context.
    def get_finam_client() -> FinamClient:
        return get_context().get_state("finam_client")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it lists the types of information retrieved, it doesn't describe behavioral traits such as authentication requirements, rate limits, whether the data is real-time or cached, error conditions, or response format. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence in Russian that lists all retrieved information types without unnecessary words. It's appropriately sized for a tool with no parameters, though it could be slightly more structured (e.g., grouping related data points). Every part of the sentence contributes to understanding what information is returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no input parameters, an output schema exists, and it's a read operation, the description is minimally adequate. It specifies the scope of returned data (account info, positions, portfolio type), which complements the output schema. However, without annotations and lacking usage guidelines, it doesn't fully prepare the agent for effective use, especially relative to sibling tools.

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?

The tool has 0 parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to explain parameters, so it meets the baseline expectation. No additional parameter semantics are required or provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: retrieving specific account information including status, type, available funds, daily profit, open positions, and portfolio type. It uses the Russian verb 'Получение' (retrieval) with the resource 'счета' (account), making the action and target explicit. However, it doesn't distinguish this from sibling tools like 'account_get_trades' or 'account_get_transactions', which likely retrieve different subsets of account data.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or compare it to sibling tools like 'account_get_trades' (which might retrieve trade history) or 'assets_get' (which might retrieve asset holdings). The agent must infer usage from the tool name and description alone.

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/FinamWeb/finam-mcp'

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