Skip to main content
Glama

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

Financial ratios of a GPW company

get_financial_ratios
Read-onlyIdempotent

GPW quarterly financial ratios from published, quality-gated reports: EBITDA, operating, net profit margins, plus equity/assets. Each percentage includes its formula and report basis. Null means missing, withheld or nonpositive denominator. No price-based valuation multiples or TTM estimates.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesGPW company ticker (for example PKNORLEN or KGHM), alias or ISIN.
quartersBackNoHow many most recent reported quarters to return, 1-20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / quartersBack / description
      Added value: +"How many most recent reported quarters to return, 1-20."
    • addedInput schema / properties / symbol / description
      Added value: +"GPW company ticker (for example PKNORLEN or KGHM), alias or ISIN."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, yet the description still adds real behavioral context: the data comes from "published, quality-gated reports," each percentage ships with its formula and report basis, and null encodes missing, withheld, or nonpositive-denominator cases. This null semantics detail is the kind of thing an agent would otherwise misread as zero or error.

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?

Four short sentences, front-loaded with the resource and metrics, then provenance, then null semantics, then exclusions. No filler and no repetition of the title or schema.

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?

With no output schema, the description carries the burden of explaining return contents, and it does: named metrics, formula/basis annotations per value, and null handling. Field names and shaping of the per-quarter response are still left implicit, but nothing essential for a correct call is missing.

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 coverage is 100%, with both symbol (ticker/alias/ISIN) and quartersBack (1-20, default 8) fully documented in the schema. The description adds no further meaning about either parameter, so the baseline of 3 applies.

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?

States a specific resource (GPW quarterly financial ratios) and enumerates the exact metrics returned: EBITDA, operating and net profit margins, equity/assets. The closing sentence excludes valuation multiples and TTM estimates, which narrows scope against price-oriented siblings, though no sibling is named directly.

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 is implied by the metric list plus the negative scope ("No price-based valuation multiples or TTM estimates"), so an agent can infer this is for margin/leverage data rather than pricing. There is no explicit when-to-use statement or pointer to the closest sibling such as get_quarterly_kpis.

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.