Skip to main content
Glama

finwire.pl - Polish financial data

Housing loan market

get_credit_market
Read-onlyIdempotent

Use for the state of the mortgage market: lending criteria, demand and new loans. Polish housing loan market: topic "index" (finwire 0-100 credit market index, returns finwire_credit_market_index), "survey" (NBP bank lending survey: criteria and demand), "monetary" (NBP household loans and deposits, new housing loans), "demand" (BIK Demand Index for housing loans, average requested vs granted amount, granted loans y/y according to BIK, new housing loans from NBP).

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": "get_credit_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoDefault index.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "index",
      -  "survey",
      -  "monetary"
      -]New value: +[
      +  "index",
      +  "survey",
      +  "monetary",
      +  "demand"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare a safe read-only, idempotent, closed-world operation, so the description is not carrying the safety burden. What it does add is data provenance and coverage — finwire index, NBP bank lending survey, NBP household loans/deposits, BIK demand index — which helps the agent trust and interpret results. It says nothing about freshness, units, or the shape of the response, but an output schema exists to cover that.

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 usage statement is front-loaded and the topic list is compact and parallel in structure. It is a single dense sentence-block, and the enumeration is long but every clause maps to a distinct enum value, so little is wasted.

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?

For a one-parameter, optional-argument tool with full annotation coverage and an output schema, the description supplies the only thing the structured fields cannot: what each topic means and where the data comes from. Only the default-topic behavior is slightly implicit, carried by the schema's "Default index."

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the schema itself only labels the single enum parameter as "Default index." The description goes well beyond that by defining what each of the four topic values actually returns, including the underlying source and metric. This is real added meaning rather than restatement, though it stops short of noting required vs. optional behavior.

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?

Opens with a specific use statement naming the resource (the Polish mortgage market) and the three data families returned: lending criteria, demand and new loans. It then breaks the tool down into four enumerated topics, so an agent understands the scope precisely. It does not, however, contrast itself with nearby siblings such as get_housing_balance, get_bank_rates or get_interest_rates, so the boundary against those is left to inference.

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?

"Use for the state of the mortgage market" gives a clear triggering context, and the per-topic breakdown effectively tells the agent which topic to pick for which question (criteria vs. demand vs. volumes). There is no explicit when-not guidance and no named alternative tool for overlapping questions, which keeps it below a 5.

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.