Skip to main content
Glama

Arc & Ledger Tax Reference

by com.arcandledger

Estimate rental property taxes

estimate_rental_income
Read-only

Use to estimate a basic rental-income result from nonidentifying figures and identify the modeled depreciation, passive-loss, and personal-use limitations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rental_daysNoDays the property was rented at fair value (short-term only).
rental_typeNolong_term (standard residential lease) or short_term (Airbnb/VRBO-style). Defaults to long_term.
land_percentNoPercent of the purchase price attributable to non-depreciable land (default 20). The building is depreciated over 27.5 years.
filing_statusNoFederal filing status. Defaults to single.
other_income_usdNoYour other taxable income (e.g. wages, business) for the year. Sets the marginal rate applied to net rental income, and gates the passive-loss allowance.
personal_use_daysNoDays YOU used the property personally (short-term only). Triggers the 14-day tax-free rule when a stay is rented 14 days or fewer and used more personally.
operating_expenses_usdNoDeductible operating expenses: mortgage interest, property tax, insurance, HOA, repairs, management, utilities, supplies. Excludes depreciation (computed for you).
annual_rental_income_usdYesGross rent received this year, before expenses.
real_estate_professionalNoWhether you materially participate as a real-estate professional under IRC 469(c)(7). If true, rental losses are not passive-limited.
property_purchase_price_usdNoWhat you paid for the property (building + land). Used to compute straight-line depreciation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
relayYesInstruction to the calling assistant: relay figures and dates verbatim (identical on every response).
next_stepYesA single review link appropriate to this server surface.
disclaimerYesGeneral-information disclaimer (identical on every response).
source_urlYesOfficial IRS or FinCEN authority to review before relying on the result.
server_versionNoServer release that produced this response (matches GET /version).

TDQS

A3.6/5.0
Behavior4/5

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

The description adds value beyond the annotations by specifying that the tool 'models depreciation, passive-loss, and personal-use limitations', giving insight into the computation. Annotations already indicate read-only (readOnlyHint=true) and non-destructive (destructiveHint=false), and the description is consistent. However, it does not detail the return format or any applicable rate limits.

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 a single sentence that efficiently conveys the tool's purpose without redundancy. It is front-loaded with the action verb 'Use to estimate'. However, it could be slightly restructured for readability, but overall it is concise.

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

Completeness3/5

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

Given the tool's complexity (10 parameters, output schema exists), the description is minimal but adequate. It states the high-level purpose and what limitations are identified. With an output schema, the return value details are covered, so the description does not need to elaborate further. However, it could provide more context on how the estimation works or assumptions made.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 10 parameters. The description mentions 'nonidentifying figures' but does not elaborate on any individual parameters beyond what the schema provides. Thus, it adds little extra meaning, meeting the baseline score of 3.

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 estimates a 'basic rental-income result' and identifies key tax limitations (depreciation, passive-loss, personal-use). The verb 'estimate' combined with the resource 'rental-income result' makes the purpose specific. It is distinct from sibling tools like 'estimate_augusta_rule' or 'estimate_quarterly_taxes' which focus on different tax scenarios.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as 'estimate_augusta_rule' or 'estimate_irs_penalty'. It simply says 'Use to estimate...' without explaining contexts where another tool would be more appropriate or any prerequisites.

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

All Arc & Ledger Tax Reference toolsInspect
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.2/5.0
Disambiguation5/5

Each tool addresses a distinct tax topic or action, such as screening obligations, checking eligibility, estimating amounts, or explaining documents. There is no overlap in purpose, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun or verb_phrase pattern (e.g., check_*, estimate_*, explain_*, decode_*, deadline_calendar). The naming is predictable and clear across the set.

Tool Count5/5

With 13 tools, the server covers a broad range of tax reference needs without being overwhelming. Each tool has a clear purpose and the count is well-suited for the domain.

Completeness4/5

The tools cover common tax reference tasks like screening obligations, estimating penalties, explaining forms, and checking deadlines. A minor gap is the lack of a general tax liability estimator, but overall the set is comprehensive for its stated purpose.

Resources