Skip to main content
Glama

Дивиденды акции

investmint_dividends

Дивиденды одной акции по тикеру. action=history — прошлые выплаты (даты отсечки и суммы), action=upcoming — ближайшая ОБЪЯВЛЕННАЯ выплата. Объявленные дивиденды и история — бесплатно. ПРОГНОЗНЫЕ дивиденды (консенсус до объявления) отдаются только по ключу тарифа с ИИ; без него в ответе стоит forecast_locked=true. Возвращает суммы в рублях на акцию, не доходность портфеля.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "investmint_dividends"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNohistory
tickerYesтикер акции, напр. SBER

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description adequately discloses behavioral traits: both history and upcoming are free, forecast dividends require a key (otherwise forecast_locked=true), and results are in rubles per share, not portfolio yield.

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 concise (a few sentences) and covers key functionality. It could be more structured (e.g., bullet points) but is still effective and not overly verbose.

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?

For a simple tool with 2 parameters and no output schema, the description explains what is returned (amounts per share, forecast_locked flag). It covers the core use cases adequately.

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 has 2 parameters (action, ticker) with 50% description coverage. The description adds meaning by explaining the action enum values and the forecast lock behavior, supplementing the schema's minimal descriptions.

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 that the tool returns dividends for a single stock by ticker, with two distinct actions (history and upcoming). It distinguishes itself from sibling tools like bond coupons or calendar by focusing on stock dividends per share.

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?

The description explains the two actions and when to use each (past payments vs. upcoming announced payment). It also mentions that forecast dividends require a tariff key, but does not explicitly contrast with alternative tools like investmint_bond_coupons.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources