Skip to main content
Glama

finwire.pl - Polish financial data

Running costs of a flat

get_housing_costs
Read-onlyIdempotent

Use for the running costs of a flat. Monthly running costs of a flat in 20 largest cities: co-op and owners association charges per m², heating, electricity, gas, water and waste rates, each with year and scope (city or province).

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or slug (e.g. "Kraków" or "krakow") ; omit for the list of cities.

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. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description contributes useful scope detail (20 largest cities, per-year, city-or-province granularity) but says nothing about omitted cities, missing years, or coverage limits.

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?

Two sentences: a front-loaded purpose statement followed by a dense enumeration of the returned cost components. The list is long but every item is substantive, and nothing is repeated verbatim from the title or annotations.

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?

Since an output schema exists, return structure need not be restated, and the description covers domain, geography, and time granularity. The only gap is telling the agent how to discover valid city values beyond the implicit omit-to-list behavior.

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?

With one parameter at 100% schema coverage, the schema already explains the city name/slug format and the omit-to-list-cities behavior. The description adds the province-vs-city scope concept but does not tie it to the city parameter, so it adds little 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 resource (monthly running costs of a flat) and enumerates the component data: co-op/owners association charges per m², heating, electricity, gas, water and waste. It is clearly a read-lookup for cost-of-living figures rather than prices or balances, though it never names a sibling to sharpen the contrast.

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?

"Use for the running costs of a flat" gives an explicit but minimal when-to-use cue. There is no guidance on when to prefer it over adjacent tools such as get_fixed_cost_burden or get_energy_prices, which plausibly overlap, so the agent must infer the boundary.

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.