Skip to main content
Glama

finwire.pl - Polish financial data

Find a dataset

search_datasets
Read-onlyIdempotent

Use when no other tool is applicable. Then use get_dataset with the id from the result. Catalog of all finwire.pl datasets (rates, FX, gold, fuel and energy prices, Finwire Nowcast, broker fees, housing prices and rents, credit market, legal limits and law changes, regional income, Europe) with the best tool to call, its parameters, license and finwire.pl page.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords in Polish or English, e.g. "czynsze", "mortgage", "podatek".
categoryNoDataset category.

Output Schema

NameRequiredDescriptionDefault
countYes
citationYes
datasetsYes
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond them by disclosing the shape of each catalog entry (tool name, parameters, license, source page), which tells the agent what it will get back and why it matters. It does not discuss result limits or ranking behavior, keeping it short of a 5.

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 decisive routing rule is front-loaded in the first sentence, followed by the follow-up step. The long parenthetical topic list is informative for coverage discovery but is the bulkiest part and could be trimmed without much loss.

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 an output schema present and full parameter documentation, the description need not explain return values, and it correctly focuses on the routing and hand-off logic. What remains unstated -- result ordering, empty-result behavior -- is minor for a discovery tool with rich annotations.

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%, so both query and category are already documented in the input schema, including the enum values and Polish/English examples. The description's topic list (rates, FX, housing, credit market, Europe) loosely signals what queries can match, but adds no syntax or matching rules. 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?

The description identifies the resource precisely: a catalog of all finwire.pl datasets, and explains what a result contains (best tool to call, its parameters, license, page). It is distinguishable from get_dataset through the explicit hand-off instruction. The only weakness is that the primary verb (search/find) is implicit rather than stated up front.

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

Usage Guidelines5/5

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

It gives an explicit selection rule -- 'Use when no other tool is applicable' -- which effectively states both when to use it and when not to. It also prescribes the follow-up step: 'Then use get_dataset with the id from the result,' removing any ambiguity about the two-step workflow.

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.