mcp

Закрытие дивидендного гэпа

investmint_gap_analytics

История дивидендных гэпов одной акции: на сколько процентов падала цена в экс-дивидендную дату, за сколько дней гэп закрывался, максимальная просадка после отсечки и за сколько дней до последнего дня покупки цена была минимальной. Сверху — сводка: доля закрытых гэпов и медиана дней закрытия. Требует ключ тарифа с ИИ. Считается по прошлым выплатам и не предсказывает будущие гэпы.

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_gap_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	сколько последних выплат вернуть
`ticker`	Yes	тикер акции, напр. SBER

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Since no annotations are provided, the description fully bears the burden. It discloses the authentication requirement (tariff key) and the limitation (past data only, no predictions). It also describes the output structure (summary and per-gap stats). Missing explicit mention of being read-only or side-effect free, but it's clearly a read operation.

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 coherent paragraph that efficiently conveys the tool's functionality and constraints. It is front-loaded with key information and every sentence adds value. Could be slightly more structured, but still concise and informative.

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?

The tool has only two simple parameters and no output schema. The description fully explains what data will be returned (per-gap details and summary statistics) and notes the tariff key requirement. This is complete for the tool's complexity.

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?

Both parameters have descriptions in the schema (100% coverage). The description adds an example for ticker ('SBER') and clarifies limit as 'how many last payments.' This provides marginal added value, so a baseline score of 3 is appropriate.

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 the tool provides historical dividend gap data for a single stock, including specific metrics like percentage drop, days to close, and max drawdown. It distinguishes itself from prediction tools by explicitly stating it does not predict future gaps.

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 that the tool requires an AI tariff key and is based on past payments, not predictions. It implicitly guides usage for historical analysis, but does not explicitly mention when not to use it or suggest alternatives among siblings.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?