iran-tax-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRAN_TAX_MCP_PROXY | No | HTTP proxy URL, or a comma-separated list of proxy URLs, used to reach the Iranian tax sites. System proxy settings are ignored. Useful outside Iran, where the sites often refuse foreign IPs. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tx_goods_searchA | Find e-invoice goods/service IDs (شناسه کالا و خدمات) and their VAT rate by description or ID. Source: the tax administration's ID system stuffid.tax.gov.ir. Active general IDs come first. Each row has the
13-digit id, description, vat_percent, type (general/specific, domestic/imported) and dates; |
| tx_regulations_searchA | Search the official tax regulation database (laws, circulars, rulings, opinions), newest first. Source: regulation.tax.gov.ir (سامانه جامع مقررات مالیاتی). Each item has id and type (pass both to tx_regulation_text), title, number, issuer, date (Jalali) and status (معتبر = in force, غیر معتبر = not). |
| tx_regulation_textA | Return the full text of one tax law, circular, ruling or opinion, or just one article of it. Source: regulation.tax.gov.ir. Gives title, kind, number, dates, issuer, the official PDF link and the text in
reading order with each article heading on its own line. Long laws come in parts: |
| tx_activity_codesA | Find tax activity codes (کد فعالیت / اینتاکد) with their VAT status and official profit ratios. Source: tax.gov.ir SearchIntaCode. Each row has the code, title, activity type (production/trade/services), vat_status (which VAT stage the activity falls in, or not subject), business group, profit_ratio (نسبت سود فعالیت, %) and gross_profit_to_sales_ratio (%), used for presumptive assessments. The ratios are not tax rates. |
| tx_property_valueA | Return the official property transaction value (ارزش معاملاتی املاک) per square metre at a map point. Source: tax.gov.ir GetAddressGeoLocation. Gives the booklet block and row, residential/office/commercial values and rent values in rial per m² (text 'عدم وجود اطلاعات' when the booklet has none), and the tax offices for that address. The caller must supply coordinates; this server does not geocode addresses. |
| tx_faq_searchA | Search the tax administration's official FAQ (پرسش های متداول) and return matching questions with links. Source: tax.gov.ir SearchFAQ. Returns question titles and their page url; open the url for the answer. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a clearly distinct resource: goods/service IDs, FAQ, regulations, regulation text, activity codes, and property values. The only near-pair (tx_regulations_search vs tx_regulation_text) is cleanly separated as a search/detail relationship, so an agent can reliably pick the right tool.
All names share a consistent tx_ prefix and snake_case, with a tx_<domain>_<action> scheme. Minor deviation is that some names encode an action (search/text) while others are pure nouns (activity_codes, property_value), but the set still reads predictably.
Six tools is well-scoped for a tax reference-data server. Each tool covers a distinct lookup category with no redundant or filler tools.
The surface covers the major tax reference domains (goods IDs, FAQ, regulations including full text, activity codes, property values) reasonably well. The main gap is that tx_property_value requires caller-supplied coordinates with no geocoding support, which a caller must work around.