Skip to main content
Glama
Sign In
ArcaTax

ArcaTax

by Accuarion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_filing_packet

Recalculates your federal Form 1040, then generates a draft IRS PDF and TXF export for filing, downloading the blank IRS form on first use.

Instructions

Recalculate, then write returns/2026_Form1040_Draft.pdf (official IRS form, numbers only) and returns/2026_return.txf. Downloads the blank f1040.pdf from irs.gov on first use.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_filing_packet"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: it writes two named files, embeds numbers-only values into the official form, and performs a network fetch of the blank f1040.pdf from irs.gov on first use. It omits overwrite behavior, whether existing files are replaced, and whether recalculation failures prevent any file from being written.

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 tight sentences front-loading the action, then the outputs, then the network dependency. No filler, no restatement of the tool name.

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?

An output schema exists, so return values need not be explained, and the description covers the operation, both artifacts, and the first-use download. What is missing is side-effect detail an agent would want for a file-writing tool with no annotations: overwrite policy and behavior on calculation error.

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?

Only one parameter (tax_year, default 2026) and schema coverage is 0%, so the description must compensate. The hardcoded "2026" in both filenames hints that tax_year drives the output path, but the description never states that relationship or what changing the year does to the generated form revision.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb chain ("Recalculate, then write") and the exact artifacts produced, including full relative paths and file formats (official IRS form PDF, TXF). This clearly differs from sibling calculate_1040_return because it produces on-disk outputs, though the definition never states that distinction explicitly.

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?

Usage is only implied: an agent can infer this is the terminal export step after calculation, but there is no explicit when-to-use, no exclusion against calculate_1040_return, and no statement of prerequisites (e.g., profile must be complete, all W-2/K-1 inputs entered).

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

Deploy Server

Other Tools