Skip to main content
Glama
freelance-tax-mcp

freelance-tax-mcp

Home office deduction

home_office

Compare simplified and regular Form 8829 home office deductions from square footage and costs, including business income limits and carryovers.

Instructions

Home office deduction: simplified ($5/sq ft, up to 300 sq ft) vs regular Form 8829 method, with the business income limit and carryovers. Give home_sqft and costs to compare both.

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": {
      "office_sqft": "<office_sqft>"
    },
    "name": "home_office"
  }
}

Input Schema

NameRequiredDescriptionDefault
rentNoRent
basisNoHome basis for depreciation (building only, not land)
directNoCosts only for the office
methodNo
monthsNoMonths used this year (default 12)
repairsNoRepairs and maintenance
home_sqftNoWhole home area in sq ft
insuranceNoHomeowner or renter insurance
utilitiesNoUtilities
other_homeNoOther whole-home costs
first_monthNoMonth the office was first used (1-12) if this is the first year
office_sqftYesOffice area in sq ft (regular and exclusive business use)
gross_incomeNoGross income from the business use of the home
other_expensesNoOther business expenses not tied to the home
prior_operatingNoCarryover of operating costs from last year
mortgage_interestNoHome mortgage interest for the year
real_estate_taxesNoReal estate taxes
prior_depreciationNoDepreciation carryover from last year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully states the simplified method rate and square-foot cap, the regular Form 8829 method, the business income limit, and carryovers, though it does not describe the comparison output or any result structure.

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?

Two sentences, front-loaded with the core comparison and key limits. Every phrase contributes to purpose or invocation context, with no filler.

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 an 18-parameter calculator with no output schema, the description covers the essential methods, limits, and carryovers well enough for selection and invocation. It falls short of fully describing the return values or guiding which cost inputs matter for each method.

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 94%, so the schema already documents nearly all parameters. The description adds only a light mention of 'home_sqft and costs' and does not meaningfully clarify the 18 parameters, and it notably omits the required office_sqft parameter from its input hint.

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 the specific tax calculation and distinguishes the two supported methods: simplified ($5/sq ft, up to 300 sq ft) and regular Form 8829. It is clearly a home office deduction calculator, not a generic tax estimate tool.

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

Usage Guidelines3/5

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

It gives a practical invocation hint ('Give home_sqft and costs to compare both'), but does not explain when to use this tool rather than siblings like estimate or tax_figures, nor when to choose simplified versus regular directly. Usage is implied rather than explicitly guided.

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