Skip to main content
Glama
cmendezs

mcp-fattura-elettronica-it

check_ritenuta_acconto

Calculate ritenuta d'acconto withholding tax for professional invoices. Specify taxable base, tax type code (RT01-RT06), and income category for valid results.

Instructions

Compute ritenuta d'acconto (withholding tax) for professional invoices.

Use this when issuing professional service invoices (TD01 or TD06) that are subject to withholding tax — typically for self-employed professionals, agents, or freelancers. Also mark the relevant line items with ritenuta='SI' in add_linea_dettaglio(), and pass the returned 'DatiRitenuta' dict to generate_fattura_xml() as dati_ritenuta.

tipo_ritenuta determines the rate: RT01/RT02 = 20% (natural person, professional/occasional), RT03/RT04 = 23.20% (agent commissions), RT05 = 4% (condominium), RT06 = 30% (employment). causale_pagamento: income category code for Mod. 770 (e.g. 'A' professional fees, 'O' occasional).

Validates: tipo_ritenuta must be in RT01–RT06. imponibile is typically the net invoice total.

On success returns {'DatiRitenuta': {...}, 'importo_ritenuta': str, 'aliquota_applicata': str, 'imponibile_ritenuta': str, 'description': str, 'legal_ref': str}. On failure returns {'error': ''}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imponibileYesTaxable base amount subject to withholding tax (imponibile della ritenuta). Usually equals the net invoice total for professional services.
tipo_ritenutaYesWithholding tax type code: RT01 (natural person, occasional work, 20%), RT02 (natural person, professional, 20%), RT03 (legal entity, agent commissions, 23.20%), RT04 (natural person, agent commissions, 23.20%), RT05 (condominium, 4%), RT06 (employment income, 30%).
causale_pagamentoYesIncome category code for withholding tax (CausalePagamento). Common values: A (professional fees), B (agent commissions), L (employment), O (occasional work), Q (commissions). See Agenzia delle Entrate Mod. 770 for the complete list.

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 the description fully carries the burden. It discloses validation (tipo_ritenuta must be RT01–RT06), return format (success with dict containing multiple fields, failure with error dict), and the tax rates for each type. This is comprehensive.

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?

The description is well-structured with clear paragraphs, front-loading the main purpose. Each sentence adds necessary information, and there is no redundancy or fluff. It is appropriately sized for the complexity of the tool.

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?

Given the absence of annotations and presence of an output schema (implied by the listed return fields), the description covers all necessary aspects: behavior, parameters, return values, validation, and integration with sibling tools. It is complete for an agent to use the tool 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?

Schema coverage is 100% with descriptions, but the description adds additional context: it explains the tax rates corresponding to each tipo_ritenuta (20%, 23.20%, etc.) and common causale_pagamento codes (A, B, etc.). It also clarifies that imponibile is typically the net invoice total, adding value beyond the schema.

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 computes withholding tax for professional invoices, specifying the invoice types (TD01/TD06) and the professional context. It distinguishes itself from sibling tools by focusing on a specific tax calculation step.

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?

The description provides explicit when-to-use guidance (professional service invoices subject to withholding tax) and integrates with other tools: marking line items with ritenuta='SI' and passing the result to generate_fattura_xml. It explains the causal chain effectively.

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/cmendezs/mcp-fattura-elettronica-it'

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