TaxCompass — Italian tax tools

search_italian_tax_sources

Read-only

Search TaxCompass's primary-source corpus and return passages to cite.

Hybrid semantic + keyword retrieval over Italian tax & company-law primary
sources: Normattiva (statute), Agenzia delle Entrate (circolari & guidance),
INPS (social security), pinned tax-year tables (IRPEF brackets, INPS rates,
forfettario thresholds & coefficienti di redditività), the ATECO 2025 code
catalogue, and EU/treaty sources.

Each result carries a `chunk_id`, `source`, and (usually) a `url`. Cite the
`url` and quote the `text`; do not assert Italian tax facts the passages
don't support. Queries work in any language, but Italian keywords improve
recall against the (Italian) legal corpus.

Args:
    query: What to search for. Keyword-dense Italian phrasing works best.
    sources: Optional subset to restrict to (see `list_tax_sources` for keys).
        Omit to search everything. Unknown keys are ignored.
    k: Max passages to return (1–12).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`k`	No
`query`	Yes
`sources`	No

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of passages returned.
`query`	Yes	The query that was run.
`passages`	Yes	Retrieved passages, most relevant first.
`disclaimer`	Yes	Usage + citation guidance.
`sources_searched`	Yes	Source keys actually searched (after filtering).

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds that it uses hybrid semantic+keyword retrieval, returns chunk_id, source, url, and text, and warns against asserting unsupported facts. No contradiction with annotations.

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 a clear opening summary, followed by details on sources, output, and parameters. Front-loaded with purpose. While thorough, it is concise for the amount of information provided.

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 tool's complexity, 0% schema coverage, and presence of output schema, the description is highly complete. It covers retrieval method, output fields, parameters, and citation instructions. No gaps identified.

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 0%, but the description fully explains each parameter: query (keyword-dense Italian phrasing), sources (optional, refer to list_tax_sources), and k (max passages 1-12). Adds meaningful guidance beyond the schema's default values and types.

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 searches TaxCompass's primary-source corpus and returns passages for citation. It lists specific sources (Normattiva, Agenzia delle Entrate, INPS, etc.) and distinguishes from siblings like calculate_italian_tax and compare_italian_regimes by focusing on retrieval and citation.

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?

Provides guidance on query language (Italian keywords improve recall), when to use (to find citations), and how to use parameters. It also instructs the agent not to assert unsupported facts. Lacks explicit when-not-to-use, but the context is clear enough.

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?