Skip to main content
Glama

Agent Rynku - Warsaw Stock Exchange (GPW) data for your agent

GPW dividend resolutions

get_public_dividends
Read-onlyIdempotent

Odczytaj znane dywidendy GPW z WZA i zakwalifikowanych decyzji emitenta, w tym zaliczki. Zwraca kwotę jednego składnika, tożsamość i generację, rodzaj, okres obrotowy, Zarząd i zgodę RN, daty i pochodzenie. Łączna kwota roczna jest tylko kontekstem. Najnowsza kompletna generacja obejmuje anulowania. Approved i upływ terminu nie dowodzą wypłaty. asOf to odświeżenie, availableAt to dostępność generacji, sourcePublishedAt może być null. Brak wejściowego historycznego asOf. Ograniczone pokrycie, bez vendor i prognoz, pusty wynik nie dowodzi braku dywidendy.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_public_dividends"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of dividend components to return, 1-100.
symbolYesGPW company ticker (for example PKNORLEN or KGHM), alias or ISIN.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of dividend components to return, 1-100."
    • addedInput schema / properties / symbol / description
      Added value: +"GPW company ticker (for example PKNORLEN or KGHM), alias or ISIN."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, so the description's job is data semantics — and it delivers: annual total is context only, the newest complete generation includes cancellations, 'Approved' plus deadline expiry does not prove payment, sourcePublishedAt may be null, and coverage is limited. What it lacks is any statement of pagination behavior or limits interplay with the total annual figure, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense but unstructured: output-field semantics, provenance caveats, and interpretation warnings are run together in telegraphic sentences with no front-loaded lead. Every clause roughly earns its place on substance, yet the packing hurts scannability, and the description is written in Polish while surrounding tool metadata is in English.

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?

No output schema exists, so the description carries the burden of describing returns, and it does enumerate the returned facets (amount, identity, generation, type, period, board approvals, dates, provenance) plus generation/cancellation semantics. Coverage and freshness caveats are also stated. A brief note on ordering or how the annual context relates to per-component rows would close the remaining gap.

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% and both parameters (symbol, limit) are fully documented in the schema, so baseline 3 applies. The description's field-level explanations (asOf, availableAt, sourcePublishedAt) concern returned data, not input parameters, so it adds no meaning to symbol or limit beyond the 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 names a specific verb and resource: reading known GPW dividends sourced from AGM resolutions and qualified issuer decisions, including advance payments. It clearly returns per-component data (amount, identity, generation, type, period). It does not explicitly contrast itself with siblings such as get_public_earnings_calendar or get_financial_ratios, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage context is implied (known/announced dividends only, no forecasts, no vendor data, no historical asOf input), which helps an agent decide when the tool applies. However, there is no explicit when-to-use/when-not-to-use framing and no routing to an alternative tool for forecasts or calendars. The caveat that an empty result does not prove the absence of a dividend is the strongest guidance present.

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.