Skip to main content
Glama

patent_box_superdeduction_audit

Read-onlyIdempotent

[Italian Patent Box 110% superdeduction & tax shield auditor. Deterministic calculation, read-only, side-effect free]. Calculates the 110% superdeduction on qualifying R&D expenses under the Italian New Patent Box (Art. 6 D.L. 146/2021) for patents, copyrighted software, and registered designs, computing IRES (24%) and IRAP (3.9%) tax savings and the 8-year recapture mechanism. Usage: Use this tool to evaluate corporate tax savings and penalty protection documentation shields for proprietary IP assets. Returns: JSON object with { companyName: string, ipAssetType: string, isEligibleForNewPatentBox: boolean, superdeductionRatePercent: number, fiscalSummary: object, penaltyProtectionActive: boolean }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyName": "<companyName>",
      "ipAssetType": "<ipAssetType>",
      "ipRegistrationTitleOrProtocol": "<ipRegistrationTitleOrProtocol>",
      "yearOfIpGrantOrRegistration": "<yearOfIpGrantOrRegistration>",
      "qualifyingExpenses": "<qualifyingExpenses>"
    },
    "name": "patent_box_superdeduction_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNameYesEnterprise legal corporate name
ipAssetTypeYesQualifying Intellectual Property asset class
irapTaxRatePercentNoIRAP regional tax rate (default: 3.9%)
iresTaxRatePercentNoIRES corporate tax rate (default: 24%)
qualifyingExpensesYesArray of annual qualifying R&D expense allocations
yearOfIpGrantOrRegistrationYesFiscal year in which IP asset was granted / registered
ipRegistrationTitleOrProtocolYesPatent application number, copyright registration ID, or design title
isRecapturePrior8YearsApplicableNoWhether to apply the 8-year lookback recapture mechanism upon IP grant
hasDocumentaryDossierForPenaltyProtectionNoWhether the formal compliance dossier has been prepared for penalty protection ex Art. 6 c. 6

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

The description restates the annotation semantics ("read-only, side-effect free") and adds "deterministic calculation," which is genuinely useful behavioral information for a tax figure. It also discloses the return object shape, which matters because no output schema exists. Beyond that it does not explain how the 8-year recapture is applied or what assumptions drive eligibility, so the added value over annotations is moderate rather than rich.

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?

The definition is front-loaded with the legal basis and scoped calculation, then gives explicit Usage and Returns lines, so an agent can extract the essentials quickly. The bracketed preamble duplicates the read-only claim already carried by annotations, which is minor waste but the only real redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, 5-required tax engine with no output schema, the description supplies the regulatory grounding, the computed outputs, and an explicit return-shape summary. Missing edges are how eligibility is determined and whether the rate parameters are ever overridden, but nothing critical for a correct invocation is absent.

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; the description earns above that by tying parameters to domain meaning — the 8-year recapture mechanism behind isRecapturePrior8YearsApplicable and "penalty protection ex Art. 6 c. 6" behind hasDocumentaryDossierForPenaltyProtection. It does not clarify the default handling for irapTaxRatePercent/iresTaxRatePercent beyond what the schema already states.

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 names a specific computation (110% superdeduction on qualifying R&D expenses under Art. 6 D.L. 146/2021), the asset classes it covers (patents, copyrighted software, registered designs), and the exact outputs computed (IRES 24%, IRAP 3.9%, 8-year recapture). This is far more specific than a restatement of the tool name and lets an agent tell it apart from the other compliance-audit 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?

"Use this tool to evaluate corporate tax savings and penalty protection documentation shields for proprietary IP assets" states a clear usage context and implicitly scopes the tool to Italian Patent Box cases. There is no explicit when-not guidance or named alternative, but none of the listed siblings covers the same regime, so the routing risk is low.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources