Skip to main content
Glama
Sign In
amar-mcp

amar-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Inflation (CPI)

am_inflation
Read-onlyIdempotent

Fetch Iran's official CPI and inflation data by month, region, group, or province from the Statistical Centre of Iran, including monthly, point-to-point, and annual changes.

Instructions

Get Iran's official consumer price index (CPI) and inflation from the Statistical Centre of Iran, latest first.

Per month: the index, the change on the previous month (monthly_pct), the change on the same month a year earlier (point_to_point_pct, the headline "inflation" figure) and the change of the 12-month average on the previous 12 months (twelve_month_avg_pct, "annual inflation"). Use region and group for a breakdown (food, housing, ...) or province for one province (no index there, no groups). newer_report appears when the portal has published a later month as PDF before its Excel series is updated.

Input Schema

NameRequiredDescriptionDefault
groupNoA CPI group: Persian name part (e.g. 'مسکن', 'خوراک', 'حمل') or its 2-digit code ('04'). Omit for the all-items index. See am_inflation_groups for the list.
monthsNoHow many latest months to return
regionNoHouseholds: all of Iran, urban or ruralnational
provinceNoProvince name (e.g. 'تهران', 'خوزستان'): returns that province's all-items inflation instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds valuable return semantics such as monthly_pct, point_to_point_pct, and twelve_month_avg_pct, plus the newer_report edge case. It does not cover rate limits, error behavior, or data revision caveats, so it is useful but not fully rich.

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?

Front-loads the core retrieval purpose, then groups output measures and parameter guidance in a compact flow with no filler. The dense technical detail is warranted because no output schema is provided.

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?

No output schema exists, so the description carries return-value explanation and does so for all four per-month measures plus newer_report. With 100% schema coverage on inputs and annotations covering safety, an agent has enough information to invoke the tool correctly.

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%, so the baseline is 3, but the description adds cross-parameter constraints: region and group enable breakdowns while province is a distinct all-items series with no index and no groups. The months parameter is only summarized as latest months and is not expanded beyond what the schema already says.

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?

Opens with a specific verb and resource — Iran's official CPI and inflation from the Statistical Centre of Iran — and names the exact per-month measures. This clearly distinguishes it from sibling price tools such as am_ppi and from the group-list helper am_inflation_groups.

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?

Explains how to choose region and group for a breakdown versus province for a single-province all-items series, including the limitation that province results have no index and no groups. It does not explicitly route the agent to or away from sibling tools like am_ppi or am_inflation_groups, so it stops short of full when/when-not guidance.

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

Deploy Server

Other Tools