taxact-mcp

Tax Document Checklist

tax_document_checklist

Read-onlyIdempotent

Returns a personalized list of tax documents and forms you need to gather before filing your tax return. Based on your income sources, deductions, and life events. Covers W-2s, 1099s, receipts, and other IRS forms. This is for DIY filers preparing their own return.

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": {
      "filing_status": "<filing_status>"
    },
    "name": "tax_document_checklist"
  }
}

Input Schema

Name	Required	Description
`filing_state`	No	Two-letter state code (e.g., "CA", "TX"). Omit for federal only.
`filing_status`	Yes	Your tax filing status
`income_sources`	No	Income types that apply to your situation
`num_dependents`	No	Number of dependents (if you selected "dependents" above)
`deductions_and_events`	No	Deductions, credits, and life events that apply

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 26, 2026
- addedInput schema / properties / filing_state / pattern
```
Added value: +"^[A-Z]{2}$"
```
First observedMay 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows it is a safe, side-effect-free operation. The description adds that the output is 'personalized' and 'based on your income sources, deductions, and life events,' providing insight into the tool's behavior beyond the annotations.

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?

The description is compact and front-loaded, with the main purpose in the first sentence. Every sentence adds value—personalization basis, coverage of specific forms, and target audience—without redundancy or fluff.

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?

Despite having 5 parameters and no output schema, the description explains enough: it returns a personalized list of documents, references the input categories, and provides examples of what is covered. Combined with the rich schema descriptions and annotations, this is complete for an agent to invoke correctly.

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 parameters are already well-documented. The description reinforces that income_sources and deductions_and_events influence the output ('Based on your income sources, deductions, and life events') but adds no new details beyond the schema. Baseline 3 is appropriate.

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 'Returns a personalized list of tax documents and forms' with the specific resource being the tax document checklist. It distinguishes itself from siblings like explain_tax_document by emphasizing the personalized list generation rather than explanation of a single document.

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 provides clear context: 'This is for DIY filers preparing their own return' and indicates it is based on income sources, deductions, and life events. It does not explicitly mention alternatives or when not to use the tool, but the context is sufficient for an agent to understand the primary use case.

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

All taxact-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?