Skip to main content
Glama
Sign In
ArcaTax

ArcaTax

by Accuarion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

upsert_1099

Add or replace 1099-INT, 1099-DIV, 1099-B, or 1099-NEC records by id to keep tax documents current for accurate 1040 calculations.

Instructions

Add or replace one or more 1099-INT / 1099-DIV / 1099-B / 1099-NEC records (matched by id). For 1099-B, send one record per sale or per broker summary line.

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": {
      "documents": "<documents>"
    },
    "name": "upsert_1099"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNo
documentsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does usefully disclose that existing records are replaced when `id` matches, which is the key destructive behavior. But it omits permissions/auth needs, whether omitted amount fields reset to 0 on replace, and whether downstream return calculations are affected.

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 short sentences, front-loaded with the core verb and resource, with the 1099-B caveat as the single follow-up. No filler or redundancy.

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?

For a four-variant upsert schema with no annotations, the description covers the essentials of what goes in and how matching works, and an output schema exists so return values need no explanation. It still leaves tax-year scoping and replace semantics for unspecified fields unaddressed, which matters when default amounts overwrite data.

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

Parameters4/5

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

Schema description coverage is effectively 0%, and the description compensates by explaining that `documents` holds multiple records of four form types discriminated by form_type, that `id` drives matching, and that 1099-B entries must be one-per-sale. It does not explain `tax_year` (which silently defaults to 2026) or the per-form required fields, keeping it below a 5.

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?

States a specific verb pair ('add or replace'), the resource (1099-INT/DIV/B/NEC records), and the matching key (`id`). That scopes it clearly against siblings like upsert_w2 and upsert_k1_1120s, though it never names those alternatives 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?

The phrase 'matched by `id`' implies an upsert rule (id present = replace, absent = add), and the 1099-B sentence gives one concrete usage rule about granularity. It gives no explicit when-to-use-vs-alternatives guidance, no mention of update_other_inputs/remove_document, and no prerequisites.

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