Georgia MCP

Get the inflation of Georgia

stats_get_inflation

Read-onlyIdempotent

Returns the inflation of Georgia for one month, in percent: annual (to the same month of the previous year), monthly (to the previous month), the 12 month average, and core inflation. For the whole country, a city, and a price group. The default is the newest published month. Data from the consumer price index of Geostat.

Input Schema

Name	Required	Description
`group`	No	The price group: total, food, alcohol_tobacco, clothing, housing, furnishings, health, transport, communication, recreation, education, restaurants, or miscellaneous. The default is total.
`month`	No	The month, YYYY-MM. The default is the newest published month.
`region`	No	georgia, tbilisi, kutaisi, batumi, gori, telavi, or zugdidi. The default is georgia.
`language`	No	The language of the names: ka or en. The default is en.

Output Schema

Name	Required	Description
`core`	Yes	The core inflation, in percent. Published for georgia and the group total only.
`as_of`	Yes	The instant at which the server read the indices, RFC 3339.
`group`	Yes	The price group.
`month`	Yes	The month, YYYY-MM.
`stale`	Yes	True when Geostat did not answer and the server returns indices it read before.
`annual`	Yes	The change of prices since the same month of the previous year, in percent. Null when not published.
`region`	Yes	The region.
`source`	Yes	The source of the data: Geostat.
`tables`	Yes	The tables of Geostat that the answer reads, with their update dates.
`average`	Yes	The change of the average prices of the last 12 months over the 12 months before, in percent. Published for the group total only.
`monthly`	Yes	The change of prices since the previous month, in percent. Null when not published.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.3/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 open-world, so the safety profile is covered. The description adds genuinely new context: the unit (percent), the exact definition of each of the four measures, the data provenance (Geostat CPI), and the default-to-latest-month behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero filler: output and unit first, dimensionality second, default and provenance last. Each sentence carries information the caller needs.

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?

With an output schema present, the description need not explain return values, and it still covers units, measure definitions, dimensionality and defaults. Nothing required for a correct zero-required-parameter call is missing.

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% and every parameter, including the full enumerations for group, region and language, is documented in the schema. The description only restates the month/region/group axes and the newest-month default, adding no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource — 'Returns the inflation of Georgia for one month, in percent' — and enumerates the four measures (annual, monthly, 12-month average, core), so it cannot be confused with the generic stats_get_table / stats_get_cells siblings.

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?

Gives clear operating context: the dimensions available (whole country, city, price group), the default of the newest published month, and the Geostat CPI source. It does not name an alternative tool or state when a caller should prefer stats_get_table instead, so it stops short of explicit routing.

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

All Georgia MCP 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.