Skip to main content
Glama

Xearno Tools

New York Statutory Residence Checker (183-Day + Abode Test)

ny_statutory_residence_checker
Read-only

Whether New York can tax you as a resident under the two-prong statutory test — the abode gate people miss, plus the 183-day count where any part of a day counts. For taxpayers NOT domiciled in New York: applies the deterministic statutory-residence test of NY Tax Law §605(b)(1)(B) — a permanent place of abode maintained for substantially all of the year AND more than 183 days of presence — plus the separate New York City test. General AI compresses this to "183 days = resident" and misses both gates: without a permanent place of abode, 300 days in NY doesn't make you a statutory resident, and with one, day 184 does — where a 20-minute stop in the state counts as a full day. Domicile (whether New York is your true home) is a separate facts-and-circumstances battle this tool does not decide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
abodeNoDo you maintain a dwelling in New York? The trap: people count days but don't know that a NYC crash pad, a company apartment principally available to you, or even a sublet counts as a "permanent place of abode". Vacation homes are generally not one (Obus, 2022); undergraduate apartments are disregarded by policy.none
daysNYNoDays with any presence in New York State Any part of a day = a full day. Only two exceptions: pure travel-through (boarding a flight or train out, driving through) and inpatient medical confinement. Outpatient visits and "just dinner in the city" days COUNT.
daysNYCNoOf those, days with any presence in the five boroughs For the separate New York City resident test. Leave 0 if NYC doesn't apply to you.
abodeInNYCNoIs the dwelling in New York City? Drives the separate city test. NYC levies its own resident income tax on top of the state's.no
abodeMonthsNoMonths of the year the dwelling was maintained "Substantially all of the year" means MORE than 10 months (Audit Division policy for tax years 2022+; it was 11 before). This matters mainly in years you acquire or dispose of the home — renting it out briefly mid-ownership does NOT break continuity.
armedForcesNoActive-duty US armed forces? Active-duty members of the US armed forces are statutorily excluded from the day-count prong.no

TDQS

A4.9/5.0
Behavior5/5

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

Despite 'readOnlyHint: true' annotations, the description adds extensive behavioral details: any part of a day counts, exceptions (travel-through, inpatient), vacation homes generally not abode, undergraduate apartments disregarded, and the NYC test. No contradiction; adds value beyond 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?

The description is front-loaded with the key insight about the abode gate, but it is quite long (several paragraphs). While every sentence adds value, it could be slightly tighter. Still well-structured with clear paragraphs.

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 complexity of statutory residence (6 parameters, legal nuances, no output schema), the description covers all critical details: the two-prong test, day-counting exceptions, abode definition, NYC separate test, and armed forces exclusion. No gaps for a taxpayer determining residency.

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 detailed enum descriptions. The description adds substantial meaning: 'abode' explains trap (crash pad counts), 'daysNY' clarifies exceptions, 'daysNYC' mentions NYC tax, 'abodeMonths' defines 'substantially all' (>10 months). Adds real semantic value beyond enum labels.

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 it checks New York statutory residence under the two-prong test (abode + 183 days) for non-domiciled taxpayers, and distinguishes it from domicile. It also notes common AI compression errors, making the purpose specific and distinct from sibling tools like 'us_substantial_presence_test'.

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 explicitly says it applies to taxpayers NOT domiciled in New York, explains the two gates (abode and days), warns that '183 days = resident' is incomplete, and separates the NYC test. It implicitly tells when not to use (if domiciled) and provides alternatives in context.

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.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool targets a distinct niche (e.g., specific country tax rules, loan types, or legal calculations), with detailed descriptions that clarify boundaries. However, the large number of tools (66) could cause some confusion for an agent trying to select the right one for a general query, especially when multiple tools relate to the same country.

Naming Consistency4/5

Tool names follow a mostly predictable pattern: lowercase words separated by underscores, often starting with a country name (e.g., 'uk_stamp_duty_sdlt') or a topic (e.g., 'compound_growth'). There are minor deviations, such as abbreviations ('npv_irr', 'sip') and varying use of verbs, but overall the naming is clear and consistent.

Tool Count3/5

At 66 tools, the server is unusually large and covers an extensive range of financial and legal calculators. While each tool justifies its existence, the count exceeds the typical well-scoped range (3–15), making the server feel bloated. A more modular design might improve coherence.

Completeness4/5

The tool set covers a wide array of domains: personal income taxes, property taxes, loan calculations, investment returns, and specific country regulations. Minor gaps exist (e.g., missing tools for corporate taxes, general retirement planning, or insurance), but the overall coverage is thorough and addresses many niche scenarios that general AI handles poorly.

Resources