Skip to main content
Glama
atomno-mcp

mcp-fns-calc

calc_penalty

Estimate late-payment tax penalties under Article 75 of the Russian Tax Code using a single CBR key rate. Input arrears amount, delay days, and payer type to get a rounded penalty figure.

Instructions

Estimate late-payment tax penalty (пени) per NK RF art. 75 using the CBR key rate.

When to use

  • Quick what-if: how much penalty accrues on a known arrears amount and delay in days.

  • Org vs IP/individual: orgs use 1/300 for days 1–30, then 1/150; IP and individuals use 1/300 for all days.

  • Before a payment plan or negotiation — ballpark figure, not a filing document.

When NOT to use

  • Multi-period calculation where the key rate changed during the delay (this tool uses one flat rate).

  • Penalties on non-tax debts (commercial loans, fines outside NK art. 75).

  • Official amount on a tax notice — always take the figure from FNS/LK; use this tool only for estimates.

Parameters

  • amount: principal arrears in RUB (non-negative).

  • days: calendar days of delay (0 → penalty 0).

  • key_rate: annual CBR %; omit to use bundled snapshot default (response includes warning_ru if default used).

  • payer: org | ip | individual — selects the 1/300 vs 1/150 split for legal entities.

Returns (dict)

  • penalty (float): total penalty in RUB, rounded to kopecks.

  • amount, days, key_rate, payer: echo inputs used in the formula.

  • formula (str): human-readable breakdown.

  • article: "ст. 75 НК РФ".

  • snapshot_date, disclaimer, source: metadata for audit trail.

  • warning_ru (optional): present when key_rate was taken from snapshot, not passed explicitly.

Limitations

  • Single key rate for the whole period; for rate changes call get_rates(fresh=true) and run per sub-period manually.

  • Does not include other sanctions (штрафы) under NK art. 122/123 — only пени art. 75.

  • Read-only, offline, deterministic; no side effects; idempotent for identical inputs.

Examples

  • Org, 100_000 RUB, 45 days, key_rate=21: days 1–30 @ amount×21%/300×30 + days 31–45 @ amount×21%/150×15.

  • IP, 50_000 RUB, 10 days: amount×rate%/300×10 for all days.

  • days=0 → penalty=0 regardless of amount.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYesЧисло календарных дней просрочки с даты, когда платёж должен был быть уплачен.
payerNoТип плательщика: org (организация), ip (ИП), individual (физлицо, не ИП).ip
amountYesСумма недоимки (руб.), на которую начисляются пени.
key_rateNoКлючевая ставка ЦБ РФ, % годовых. Если не задана — берётся из встроенного снапшота (см. snapshot_date в ответе).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description fully handles disclosure. It states read-only, offline, deterministic, no side effects, idempotent, and lists limitations like single key rate and exclusion of other sanctions.

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?

Well-structured with sections and bullet points, every sentence adds value. Slightly long but necessary for a complex tax tool. No redundancy.

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?

Comprehensive coverage: purpose, when-to-use/not, parameter explanations, return value details (dict fields), limitations, and examples. Output schema referenced. Full context for an AI agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds significant meaning beyond schema: explains amount as principal arrears, days as calendar delay, key_rate as optional with default warning, and payer selecting penalty split. Includes examples illustrating parameter usage.

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 clearly states the tool estimates late-payment tax penalty under NK RF art. 75 using CBR key rate. It distinguishes from siblings like calc_insurance_ip by focusing on tax penalties.

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?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance. It mentions context (quick what-if, before payment plan) and exclusions (multi-period, non-tax debts, official amounts).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/atomno-mcp/mcp-fns-calc'

If you have feedback or need assistance with the MCP directory API, please join our Discord server