Finam MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap, organized by functional categories like account, assets, market data, and orders. For example, account_get_info, account_get_trades, and account_get_transactions cover different aspects of account data without ambiguity, and similar clarity exists across all tools.
Naming Consistency5/5
All tool names follow a consistent pattern of 'category_verb_noun' (e.g., account_get_info, market_data_get_bars, order_place), using snake_case throughout. This predictable structure makes it easy to understand each tool's function and domain at a glance.
Tool Count5/5
With 17 tools, the server is well-scoped for a financial trading domain, covering account management, asset information, market data, and order operations. Each tool serves a specific, necessary function without redundancy, fitting within the typical 3-15 range for such a comprehensive service.
Completeness5/5
The tool set provides complete coverage for financial trading, including CRUD operations for orders (place, get, list, cancel), detailed account and asset data, and comprehensive market data access. There are no obvious gaps; agents can perform full trading workflows from research to execution and monitoring.
Average 2.9/5 across 17 of 17 tools scored. Lowest: 1.7/5.
See the Tool Scores section below for per-tool breakdowns.
This repository is archived. Archived repositories automatically receive an F maintenance tier.
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure but provides none. It doesn't mention that this is a potentially destructive/mutative operation (placing orders typically involves financial transactions), what permissions are required, rate limits, error conditions, or what happens on success. The description is completely inadequate for a financial transaction tool.
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 maximally concise - a single phrase that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. While this conciseness comes at the cost of completeness, the description itself is efficiently structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex financial order placement tool with a rich input schema (Order object with 11 properties, multiple enums) and no annotations, the description is completely inadequate. It doesn't explain what the tool does beyond the name, provides no parameter guidance, no behavioral context, and no usage guidelines. The existence of an output schema doesn't compensate for these fundamental gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, meaning the schema provides no parameter descriptions. The tool description adds no parameter information whatsoever - it doesn't mention the 'order' parameter, what it contains, or how to structure it. For a complex tool with a nested Order object containing 11 properties, this is a critical deficiency.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Выставление биржевой заявки' (Placing a stock exchange order) is a tautology that essentially restates the tool name 'order_place'. It doesn't specify what type of order (market, limit, stop, etc.) or provide any distinguishing details from sibling tools like 'order_cancel' or 'order_get'. While it indicates the general domain, it lacks specificity about the actual operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/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. There are multiple sibling tools related to orders (order_cancel, order_get, order_get_list), but the description doesn't indicate this is for creating new orders versus managing existing ones. No prerequisites, context, or exclusion criteria are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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. It states it's a read operation ('получение' - getting), implying it's likely non-destructive, but doesn't specify authentication requirements, rate limits, pagination behavior (beyond the limit parameter), or what constitutes a 'transaction' (e.g., deposits, withdrawals, trades). For a tool with no annotation coverage, this leaves significant behavioral gaps.
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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a basic tool, though it could benefit from being more informative. The structure is straightforward, but it lacks front-loading of critical details like differentiation from siblings.
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 an output schema (which should document return values), the description doesn't need to explain outputs. However, with no annotations, 3 parameters (2 required), and 0% schema coverage, the description is incomplete—it doesn't address key contextual aspects like authentication, error handling, or transaction scope. It's minimally adequate but has clear gaps in guiding the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, meaning none of the parameters (start_time, end_time, limit) are documented in the schema. The description adds no parameter information beyond what's implied by the tool name—it doesn't explain what time ranges are valid, the format of transactions returned, or how the limit parameter interacts with pagination. With low schema coverage, the description fails to compensate, leaving parameters largely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Получение списка транзакций аккаунта' (Getting a list of account transactions) clearly states the verb ('получение' - getting) and resource ('транзакций аккаунта' - account transactions), but it doesn't differentiate from sibling tools like account_get_trades or account_get_info. The purpose is understandable but lacks specificity about what distinguishes this transaction retrieval from other account-related operations.
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. There's no mention of prerequisites, context for usage, or comparison with sibling tools like account_get_trades (which might retrieve trade-related transactions) or order_get_list (which might retrieve order-related transactions). The agent must infer usage from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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. It states this is for 'Получение информации' (Getting information), which suggests a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what happens if the order ID is invalid. For a tool with zero annotation coverage, this is a significant gap.
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, front-loaded with the core purpose. There's no wasted text, making it appropriately sized for a simple tool. However, it could be more structured if it included additional details.
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 1 parameter, no annotations, but an output schema exists, the description is minimally complete. The output schema likely covers return values, so the description doesn't need to explain those. However, for a read operation with no annotations, it should provide more context on behavior and parameters to be fully helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description doesn't add any meaning beyond what the input schema provides. It mentions 'конкретном ордере' (specific order), which hints at the 'order_id' parameter, but doesn't explain its format, constraints, or examples. With 1 parameter and low coverage, the description fails to compensate adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Получение информации о конкретном ордере' (Getting information about a specific order) states the basic purpose with a verb ('Получение' - Getting) and resource ('ордере' - order). However, it's vague about what specific information is retrieved and doesn't distinguish from sibling tools like 'order_get_list' or 'order_cancel' beyond mentioning 'конкретном' (specific).
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?
No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an order ID), exclusions, or comparisons to siblings like 'order_get_list' for multiple orders or 'order_cancel' for modifications. The description implies usage for a single order but lacks explicit context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It implies a read-only operation ('Получение' means 'getting'), but doesn't specify authentication needs, rate limits, pagination behavior, or what the output contains. For a tool with three parameters and an output schema, this leaves significant gaps in understanding how it behaves beyond basic purpose.
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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a basic tool, though it could be more front-loaded with key details given the lack of annotations and parameter documentation.
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's moderate complexity (3 parameters, 2 required), no annotations, and an output schema, the description is minimally adequate. The output schema helps offset some completeness needs, but the description lacks details on usage context, parameter meanings, and behavioral traits, making it incomplete for optimal agent understanding.
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?
Schema description coverage is 0%, so the schema provides no parameter descriptions. The tool description doesn't mention any parameters, leaving all three (start_time, end_time, limit) undocumented. However, with an output schema present, some context is inferred, but the description fails to compensate for the coverage gap, resulting in minimal added value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the purpose as 'Получение истории по сделкам аккаунта' (Getting account trade history), which clearly indicates a read operation for trade data. However, it's somewhat vague about scope and doesn't distinguish from sibling tools like 'account_get_transactions' or 'order_get_list', leaving ambiguity about what specific trade data it returns versus those alternatives.
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?
No guidance is provided on when to use this tool versus alternatives. With siblings like 'account_get_transactions' and 'order_get_list' that might overlap in functionality, the description offers no context about differences, prerequisites, or appropriate use cases, leaving the agent to guess based on tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It only states what the tool does ('getting trading schedule') without describing response format, error conditions, rate limits, authentication requirements, or whether this is a read-only operation. For a tool with no annotation coverage, this is insufficient behavioral context.
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 that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. However, it could be slightly more front-loaded with key information about the type of data returned (trading schedule vs. other asset data).
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 an output schema (which handles return values) and 100% schema coverage for the single parameter, the description is minimally adequate. However, for a tool with no annotations, it should provide more behavioral context about what a 'trading schedule' contains, typical use cases, or limitations. The description meets basic requirements but leaves gaps in operational understanding.
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?
Schema description coverage is 100%, with the single parameter 'symbol' well-documented in the schema with format, examples, and pattern. The description doesn't add any parameter semantics beyond what the schema already provides. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't need to.
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 action ('Получение' - 'Getting') and the resource ('расписания торгов' - 'trading schedule') for a specific instrument. It distinguishes from siblings like assets_get (general asset info) and assets_get_params (asset parameters), but doesn't explicitly contrast with them. The purpose is specific but lacks explicit sibling differentiation.
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. There are related tools like assets_get_exchanges (exchange info) and market_data_get_bars (market data), but the description doesn't indicate when trading schedule data is needed versus other asset or market data. No context about prerequisites or typical use cases is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but offers minimal behavioral context. It states it retrieves historical aggregated candles but doesn't disclose rate limits, authentication requirements, data freshness, whether it's a read-only operation, what happens with invalid time ranges, or pagination behavior. For a data retrieval tool with 4 parameters, this leaves significant behavioral uncertainty.
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 a single, efficient Russian sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a data retrieval tool and front-loads the core functionality. Every word earns its place in conveying the essential action.
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 4 parameters with low schema coverage (25%) and no annotations, but does have an output schema (which handles return values), the description is minimally adequate. It identifies the tool as historical data retrieval but lacks sufficient guidance on usage, parameters, and behavioral traits. The output schema reduces the need to describe return values, but other gaps remain significant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25% (only the symbol parameter has a description), so the description must compensate but adds no parameter information. It mentions 'агрегированные свечи' (aggregated candles) which hints at the timeframe parameter's purpose, but doesn't explain start_time/end_time formats, symbol format requirements beyond the schema's pattern, or timeframe enum meanings. The description provides minimal value beyond what the sparse schema offers.
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 verb ('Получение' - getting/retrieving) and resource ('исторических данных по инструменту' - historical data for an instrument), specifying it provides aggregated candles. It distinguishes from siblings like market_data_get_last_quote (real-time quotes) and market_data_get_last_trades (recent trades). However, it doesn't explicitly mention it's for historical OHLC/bar data versus other historical data types.
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 when to choose this over market_data_get_last_quote for current prices, or assets_get for instrument metadata, or specify prerequisites like needing market data access. Usage is implied by the name but not explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It implies a destructive mutation ('cancel'), but doesn't disclose behavioral traits like whether cancellation is reversible, requires specific permissions, has rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.
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 a single, efficient phrase in Russian that directly states the tool's action. It's front-loaded with the core purpose and has zero wasted words, making it highly concise and well-structured for its minimal content.
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's complexity (a destructive mutation with one parameter) and the presence of an output schema (which may cover return values), the description is minimally complete but inadequate. It states what the tool does but lacks usage context, parameter details, and behavioral disclosures. With no annotations and low schema coverage, it should provide more guidance to be fully helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It doesn't mention the 'order_id' parameter at all, leaving its meaning and format undocumented. The description adds no semantic value beyond what the bare schema provides, failing to explain what 'order_id' represents or how to obtain it.
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 'Отмена биржевой заявки' (Cancellation of exchange order) clearly states the verb ('cancel') and resource ('exchange order'), making the purpose unambiguous. It distinguishes from siblings like order_place (create) and order_get (read), though it doesn't explicitly name alternatives. The purpose is specific but could be more precise about what type of order is being canceled.
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 (e.g., an existing order), exclusions, or contextual cues. Given siblings like order_get_list and order_get, there's no indication of when cancellation is appropriate versus querying orders.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states it retrieves a list but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or whether it's a read-only operation. The description is minimal and lacks essential context for safe invocation.
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 directly states the purpose without unnecessary words. It's appropriately sized for a no-parameter tool, though it could be slightly more structured by front-loading key details like 'list all instruments' more explicitly.
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 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, as a read operation with no annotations, it should ideally mention it's safe and list-oriented to compensate for the lack of structured behavioral hints, which it doesn't fully do.
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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any parameters, earning a baseline score of 4 for this context.
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 verb ('Получение' - 'Getting') and resource ('списка доступных инструментов' - 'list of available instruments'), specifying it retrieves instruments with their descriptions including symbols and names. However, it doesn't explicitly differentiate from sibling tools like 'assets_get' which might retrieve a single asset rather than a list.
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?
No guidance is provided on when to use this tool versus alternatives. With siblings like 'assets_get' (likely for single asset), 'assets_get_exchanges', and 'assets_get_params', the description doesn't indicate this is for listing all available instruments versus filtered or specific queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It describes the data returned (prices, volumes) but lacks behavioral details like rate limits, authentication needs, latency, or error conditions. For a read-only tool with no annotations, this is a significant gap in transparency.
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 listing key data fields. It is appropriately sized for a simple retrieval tool, though it could be more front-loaded by stating the core purpose first before details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (1 parameter), high schema coverage (100%), and presence of an output schema, the description is reasonably complete. It covers the purpose and data returned, though it lacks behavioral context which is partially mitigated by the structured data.
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?
Schema description coverage is 100%, with the symbol parameter well-documented in the schema (format, examples, pattern). The description adds no parameter-specific information beyond implying 'instrument' maps to 'symbol', so it meets the baseline of 3 without compensating value.
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 verb 'получение' (retrieval) and the resource 'последней котировки инструмента' (last quote of an instrument), with specific data fields listed. It distinguishes from siblings like market_data_get_bars (historical bars) and market_data_get_last_trades (last trades), though not explicitly named.
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?
No explicit guidance on when to use this tool versus alternatives like market_data_get_bars for historical data or market_data_get_order_book for depth. The description implies it's for the most recent quote data, but lacks context on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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. It states it's a read operation ('Получение' - 'Getting'), implying it's non-destructive, but doesn't mention authentication requirements, rate limits, pagination, or what the output contains (though an output schema exists). For a tool with no annotations, this leaves significant gaps in understanding its behavior.
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 a single, clear sentence in Russian that directly states the tool's purpose without any fluff. It's front-loaded and efficiently communicates the core function, making it easy to parse quickly. Every word earns its place, and there's no wasted verbiage.
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 one parameter with full schema coverage and an output schema, the description is minimally adequate. However, it lacks context on usage guidelines, behavioral traits (like authentication needs), and doesn't leverage the output schema to hint at return values. For a simple read tool, it's functional but could be more informative to fully guide an agent.
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 description doesn't add any parameter information beyond what's in the input schema, which has 100% coverage and fully documents the single 'symbol' parameter with examples and pattern. Since schema coverage is high, the baseline is 3, and the description doesn't compensate with additional context like default behavior or constraints, so it remains at 3.
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 action ('Получение' - 'Getting') and resource ('списка последних сделок по инструменту' - 'list of last trades for an instrument'), making the purpose immediately understandable. It distinguishes from siblings like market_data_get_bars (historical data) and market_data_get_last_quote (quote data), though not explicitly. However, it doesn't specify what 'last trades' means (e.g., time window, count), keeping it from a perfect score.
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 when to choose this over market_data_get_bars (for historical trades) or account_get_trades (for user-specific trades), nor does it specify prerequisites like authentication or rate limits. The context is implied by the tool name but not explicitly stated in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. While it indicates this is a read operation ('Получение' - getting), it doesn't mention important behavioral aspects like whether this requires authentication, rate limits, what format the order book data returns, or any constraints on symbol availability. The description is minimal and lacks behavioral context.
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 extremely concise - a single Russian phrase that directly states the tool's purpose. There's zero wasted language, and it's front-loaded with the essential information. Every word earns its place in this minimal description.
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 that this is a read operation with one well-documented parameter and an output schema exists (which handles return values), the description is minimally adequate. However, for a market data tool that likely has behavioral constraints (rate limits, authentication needs, symbol availability), the description should provide more context about these aspects since no annotations are present.
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 description doesn't add any parameter information beyond what's already in the schema. With 100% schema description coverage and a well-documented 'symbol' parameter that includes description, examples, and pattern, the schema does all the work. The baseline score of 3 is appropriate since the description doesn't compensate but doesn't need to given the comprehensive schema.
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 'Получение текущего стакана по инструменту' (Getting the current order book for an instrument) clearly states the verb ('Получение' - getting) and resource ('стакана по инструменту' - order book for an instrument). It's specific about what data is retrieved, though it doesn't explicitly differentiate from siblings like 'market_data_get_last_quote' or 'market_data_get_last_trades' beyond the obvious 'order book' vs 'quote/trades' distinction.
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 when this tool is appropriate compared to other market data tools like 'market_data_get_bars' or 'market_data_get_last_quote', nor does it specify any prerequisites or exclusions for its use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 states what information is retrieved, it doesn't describe the tool's behavior beyond that—such as whether it's a read-only operation (implied but not stated), error handling, response format, or any limitations. For a tool with no annotation coverage, this leaves significant gaps in understanding how it operates.
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 a single, efficient sentence in Russian that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes to understanding what the tool does.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (1 parameter, no nested objects) and the presence of an output schema (which handles return values), the description is reasonably complete. It specifies the type of information retrieved, which complements the structured data. However, it lacks behavioral context like error cases or usage constraints, which would be beneficial despite the output schema.
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 description coverage is 100%, with the parameter 'symbol' fully documented in the input schema (including format, examples, and pattern). The description adds no additional parameter semantics beyond what the schema provides, such as explaining the MIC part or how symbols are structured. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.
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 action ('Получение информации' - getting information) and the resource ('по конкретному инструменту' - about a specific instrument), with specific examples of what information is retrieved (lot, price step, futures expiration date). It distinguishes from siblings like assets_get_list (which likely lists multiple assets) and assets_get_params (which might get different parameters). However, it doesn't explicitly differentiate from all siblings like assets_get_exchanges or assets_get_schedule.
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 when to use assets_get versus assets_get_list (for multiple assets) or assets_get_params (for different parameters), nor does it specify prerequisites like authentication requirements or rate limits. 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.
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. It states the tool retrieves a list, implying a read-only operation, but doesn't cover aspects like authentication requirements, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.
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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to quickly understand the core functionality.
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's simplicity (0 parameters, output schema exists), the description is minimally adequate. It explains what the tool does but lacks behavioral context and usage guidelines. With an output schema, it doesn't need to detail return values, but the absence of annotations means more behavioral disclosure would be helpful for completeness.
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%, so no parameter documentation is needed. The description doesn't add parameter-specific information, but this is acceptable given the lack of parameters. A baseline score of 4 is appropriate as the description doesn't need to compensate for any parameter gaps.
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: 'Получение списка доступных бирж' (Getting a list of available exchanges). It specifies the verb (getting/retrieving) and resource (exchanges), and mentions the included data (names and MIC codes). However, it doesn't explicitly differentiate from sibling tools like 'assets_get' or 'assets_get_list', which might also retrieve asset-related 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, context for usage, or compare it to sibling tools such as 'assets_get' or 'market_data_get' tools. This leaves the agent without clear direction on appropriate use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does ('retrieval'), but doesn't disclose whether this is a read-only operation, if it requires authentication, has rate limits, returns real-time or delayed data, or what happens on errors. For a financial data tool with zero annotation coverage, this is a significant gap in behavioral context.
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 a single, efficient sentence in Russian that directly states the tool's purpose with zero wasted words. It's appropriately sized for a tool with one parameter and good schema documentation, though the language barrier might affect accessibility for non-Russian speaking agents.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (which handles return values), 100% schema description coverage for the single parameter, and no complex nested structures, the description is reasonably complete. The main gaps are the lack of behavioral context (especially with no annotations) and usage guidelines, but for a relatively simple retrieval tool, it provides adequate context.
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 description coverage is 100%, with the single parameter 'symbol' fully documented in the input schema (including format, examples, pattern, and type). The description doesn't add any parameter semantics beyond what's already in the schema, so it meets the baseline of 3 when the schema does the heavy lifting.
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 action ('Получение' - 'Retrieval') and the resource ('цепочки опционов для базового актива' - 'options chain for the underlying asset'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'assets_get' or 'assets_get_params', which could also retrieve asset-related data but for different purposes.
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 sibling tools like 'assets_get' (which might retrieve general asset info) or 'market_data_get' tools (which might provide other market data), leaving the agent to infer usage context solely from the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a retrieval operation ('Получение'), it doesn't describe authentication requirements, rate limits, error conditions, response format, or whether this is a real-time or cached data source. For a financial data tool with zero annotation coverage, this represents significant behavioral gaps.
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 a single, efficient sentence that clearly states the tool's purpose. It's appropriately sized for a single-parameter retrieval tool and front-loads the essential information. Every word earns its place by specifying what trading parameters are retrieved.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (which handles return values), 100% schema description coverage for the single parameter, and relatively simple functionality (retrieval of trading parameters), the description is reasonably complete. However, the lack of behavioral context (especially with no annotations) and usage guidance prevents a perfect score for this financial data tool.
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?
Schema description coverage is 100%, so the schema fully documents the single parameter's format, pattern, and examples. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter information in the description.
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 action ('Получение' - retrieval) and the resource ('торговые параметры по инструменту'), specifying what financial parameters are obtained. It distinguishes from siblings like assets_get (general asset data) and assets_get_list (asset listings) by focusing specifically on trading parameters. However, it doesn't explicitly contrast with market_data_get tools that provide different market 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?
No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or contrast with sibling tools like assets_get (which might provide different asset information) or market_data_get tools that provide different types of market data. 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.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states it retrieves a list of orders for an account but doesn't describe what the list includes (e.g., all orders, filtered by status), how it's paginated, any rate limits, authentication needs, or the return format. This leaves significant gaps for a tool that likely interacts with financial data.
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 a single, efficient sentence in Russian that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.
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 0 parameters, 100% schema coverage, and an output schema exists (which handles return values), the description's minimalism is somewhat acceptable. However, for a tool in a financial context with siblings like 'order_get' and 'order_cancel', more behavioral context (e.g., what orders are included, any filters) would improve completeness, as annotations are absent.
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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, and the baseline for 0 parameters is 4, as it avoids unnecessary detail while matching the schema's simplicity.
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 verb ('Получение' - 'Getting') and resource ('списка заявок' - 'list of orders') for a specific account, making the purpose understandable. However, it doesn't differentiate from sibling tools like 'order_get' (which presumably gets a single order) or specify what type of orders are included (open, closed, all).
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?
No guidance is provided about when to use this tool versus alternatives. The description doesn't mention when to use 'order_get_list' versus 'order_get' (for single orders) or 'account_get_trades' (which might overlap with order data), nor does it specify prerequisites or context for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![finam-mcp MCP server](https://glama.ai/mcp/servers/FinamWeb/finam-mcp/badges/card.svg)](https://glama.ai/mcp/servers/FinamWeb/finam-mcp)

Score Badge

Copy to your README.md:

[![finam-mcp MCP server](https://glama.ai/mcp/servers/FinamWeb/finam-mcp/badges/score.svg)](https://glama.ai/mcp/servers/FinamWeb/finam-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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