tvrtke

search_financial_screener

An advanced financial screener and discovery engine for Croatian companies based on FINA statutory filings for a specific reporting year (default 2024). Supports range filtering for revenue (total_income), operating income, net profit, total assets, liabilities, equity, profit before tax, estimated EBITDA, and equity solvency ratios. Results can be sorted and paginated. RULES: Never invent financial thresholds or company profiles. If screening criteria are not provided, interview the user first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_financial_screener"
  }
}

Input Schema

Name	Required	Description
`city`	No	Filter by city / municipality
`year`	No	Target financial reporting year (default 2024)
`limit`	No	Number of results (default 20, max 100)
`county`	No	Filter by county / Županija
`offset`	No	Pagination offset
`sort_by`	No	Metric to sort by (e.g. total_income, profit_for_the_year). Default total_income
`nkd_codes`	No	Filter by primary NACE/NKD industry activity codes
`max_ebitda`	No	Maximum estimated EBITDA (operating income - expenses)
`max_equity`	No	Maximum capital and reserves (equity)
`min_ebitda`	No	Minimum estimated EBITDA (operating income - expenses)
`min_equity`	No	Minimum capital and reserves (equity)
`sort_order`	No	Sort direction: asc or desc. Default desc
`is_profitable`	No	Filter profitable (true) or loss-making (false) companies
`max_net_profit`	No	Maximum net profit/loss
`min_net_profit`	No	Minimum net profit/loss
`size_indicators`	No	Filter by size classifications (e.g. Mikro, Mali, Srednji, Veliki)
`max_equity_ratio`	No	Maximum solvency / equity ratio (0.0 to 1.0)
`max_total_assets`	No	Maximum total assets
`max_total_income`	No	Maximum revenue / total income
`min_equity_ratio`	No	Minimum solvency / equity ratio (0.0 to 1.0)
`min_total_assets`	No	Minimum total assets
`min_total_income`	No	Minimum revenue / total income
`max_operating_income`	No	Maximum operating revenue
`min_operating_income`	No	Minimum operating revenue
`max_profit_before_tax`	No	Maximum profit before tax
`max_total_liabilities`	No	Maximum total liabilities
`min_profit_before_tax`	No	Minimum profit before tax
`min_total_liabilities`	No	Minimum total liabilities

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the data source (FINA statutory filings), a default reporting year (2024), that filtering is range-based, and that results can be sorted and paginated. It does not describe the return shape, what a result row contains, result ordering guarantees, or performance characteristics of a 28-filter query.

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?

Front-loaded with what the tool is and what it filters, followed by a compact RULES block. Every sentence is functional; the only minor inefficiency is that the metric list partially duplicates the schema. No filler or redundancy otherwise.

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?

For a 28-parameter search tool with no output schema, the description covers filtering, sorting, pagination, and the data source, but never describes what the returned records look like or what fields come back. Given the absence of an output schema, a brief note on the result shape would materially complete the definition.

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 already documents every parameter, and the description's enumeration of filterable metrics (revenue, operating income, net profit, assets, liabilities, equity, PBT, EBITDA, solvency ratios) largely mirrors the schema. It adds no units, currency, or range-format detail beyond what the schema provides, so baseline 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 verb+resource: a 'financial screener and discovery engine for Croatian companies based on FINA statutory filings.' It is clearly differentiated from single-company getters like get_company_financials by being a multi-company discovery tool, but it never names a sibling (e.g. search_companies) to draw the boundary explicitly.

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?

The RULES line gives a precondition ('If screening criteria are not provided, interview the user first') and a constraint ('Never invent financial thresholds'), which is real usage guidance. However, it gives no alternatives or when-to-use-vs-siblings guidance, so the reader must infer that this is the tool for multi-criteria financial filtering rather than keyword search.

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

All tvrtke 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?