TaxCompass — Italian tax tools

compare_italian_regimes

Read-onlyIdempotent

Compare all Italian regimes side by side at one revenue level.

Runs forfettario (5% & 15%), ordinario, and ordinario + impatriati through
the deterministic engine and returns them sorted by net income (best first),
each with its full breakdown and eligibility.

Args:
    revenue_eur: Gross annual revenue in EUR.
    coefficient: Forfettario coefficiente di redditività (0.40–0.86); omit
        for the professional-services default (0.78).
    cost_ratio: Deductible costs as a fraction of revenue (0–1) for the
        ordinario regimes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cost_ratio`	No
`coefficient`	No
`revenue_eur`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`results`	Yes	One breakdown per regime, best net income first.
`disclaimer`	Yes
`revenue_eur`	Yes	Gross annual revenue (EUR) the regimes were evaluated at.

TDQS

A4.8/5.0

Behavior5/5

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

Discloses that the tool runs a deterministic engine, sorts results by net income best-first, and returns full breakdowns and eligibility. This adds meaningful behavior beyond the readOnlyHint and idempotentHint annotations, and does not contradict them.

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-loaded one-sentence purpose followed by a compact behavioral summary and an organized Args list. Every sentence adds useful information; there is no filler or 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?

Complete for a three-parameter comparison tool with an output schema: it covers inputs, defaults, return behavior, and sorting. No critical context needed for correct invocation is missing.

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?

The input schema has 0% description coverage, but the description defines all three parameters with units, ranges, defaults, and regime applicability. This fully compensates for the missing schema descriptions.

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?

States a specific verb (compare) and resource (Italian regimes), and further specifies it runs all three regimes and returns them sorted by net income. This clearly distinguishes it from sibling calculate_italian_tax, which likely handles a single regime.

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?

The description clearly conveys the use case: side-by-side comparison of all regimes at a single revenue level. It does not explicitly name calculate_italian_tax as an alternative or state when not to use this tool, so it falls short of a 5.

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

All TaxCompass — Italian tax tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: calculate targets one specific regime, compare evaluates all regimes side-by-side, and the two source tools cleanly separate listing available sources from searching their contents. There is no realistic risk of selecting the wrong tool for a task.

Naming Consistency4/5

Tool names follow a consistent lowercase snake_case verb-first pattern, e.g. calculate_italian_tax, compare_italian_regimes, search_italian_tax_sources. The one minor deviation is list_tax_sources, which omits the 'italian' descriptor that appears in the other source/search tool.

Tool Count5/5

Four tools is a well-scoped size for this server's purpose: two calculation/regime tools and two source-discovery/search tools. Each tool has a distinct and necessary role, with no redundant or filler tools.

Completeness4/5

The set covers the main workflows: single-regime calculation, cross-regime comparison, source discovery, and corpus search. Minor gaps exist, such as no explicit tax-year selection and no direct tool for retrieving raw tax tables outside of search, but the source search tool can mitigate these.

Resources

Need Help?