finwire.pl - Polish financial data

Daily price index finwire (online shelf prices)

get_daily_price_index

Read-onlyIdempotent

Use for daily online prices of a basket of food, household and personal care products. For official CPI, use get_macro_indicator. Experimental daily index of online shelf prices of a fixed basket of food, drinks, household and personal care products in three Polish online shops (finwire_daily_price_index), base month = 100: latest value and change since the base month, basket categories with change since the base month and month on month, categories with the largest rise and fall, monthly readings, the food part vs GUS CPI food and non-alcoholic beverages for the same completed month, and the collection state (days, products, stores, expected first reading) while the base month is being collected. Online prices only, not CPI; no prices of single products or shops.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`url`	Yes
`asOf`	No
`data`	No
`title`	Yes
`source`	Yes
`docsUrl`	Yes
`license`	Yes
`summary`	Yes
`citation`	Yes
`datasetId`	Yes
`sourceUrl`	No
`truncated`	No
`serverDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context, which it does: it flags the index as experimental, defines base month = 100, lists the three-shop basis, and warns that while the base month is being collected the payload includes a collection state with expected first reading. That partial-data signal is genuinely useful and not derivable from 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?

The guiding sentence and the CPI alternative are front-loaded, and the closing exclusions land well. The middle enumerates many payload components in a single long run-on sentence, which is dense but each item carries information, so the length is mostly earned rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with a declared output schema, nothing an agent needs to call it correctly is missing: scope, base month, data source, comparison series, exclusions, and the incomplete-collection caveat are all stated. It arguably over-delivers by describing return content that the output schema already covers.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning left to convey. The description does not waste effort restating arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope: an experimental daily index of online shelf prices for a fixed basket across three Polish online shops, base month = 100. It also explicitly separates itself from get_macro_indicator (official CPI), so an agent can tell the two apart without opening either schema.

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 states the use case up front ('Use for daily online prices of a basket of food, household and personal care products'), names the alternative for the CPI case (get_macro_indicator), and closes with explicit exclusions ('Online prices only, not CPI; no prices of single products or shops'). When-to-use, when-not-to-use, and the alternative are all present.

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

All finwire.pl - Polish financial data 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.