Skip to main content
Glama

finwire.pl - Polish financial data

Rents and rental yield

get_rents
Read-onlyIdempotent

Use for rents and rental yield. Asking rents (median, per m², month-over-month change) in Polish cities and districts, with gross and net rental yield and payback period.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or slug (e.g. "Kraków" or "krakow") for its districts; omit for all 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 and closed-world, so safety behavior needs no restatement. The description adds the useful scope note that results span cities and districts and include derived metrics, but says nothing about data recency, source, coverage gaps or pagination. Adequate but not rich beyond the annotations.

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 tight sentences with the domain statement front-loaded and the metric list second. The opening "Use for rents and rental yield" largely restates the title, which is the only wasted phrasing.

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-optional-parameter read tool with a full output schema and complete annotations, the description supplies enough domain context for correct selection and invocation. The missing piece is data recency/vintage, which the output schema may or may not cover.

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?

There is exactly one optional parameter and the schema describes it fully (city name or slug, omit for all cities). The description adds no additional semantics about the city filter, so the baseline of 3 applies with the schema doing the work.

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 states a specific resource (asking rents for Polish cities/districts) and enumerates the metrics returned: median rent, per m², month-over-month change, gross/net yield and payback period. That is far more concrete than the bare name and clearly separates it from sibling price/cost tools. It does not name a sibling alternative, keeping it short of a 5.

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 rents and rental yield" gives an implied when-to-use but no exclusions or explicit alternatives (e.g. versus get_housing_prices or get_housing_costs). The only scoping guidance — omit city for all cities — lives in the schema, not the description, so usage guidance is minimal but present.

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.