Skip to main content
Glama
Sign In
ArcaTax

ArcaTax

by Accuarion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_document

Deletes a W-2, 1099, Schedule C, Schedule E, or K-1 record by document ID after user confirmation, helping remove or correct tax documents in ArcaTax.

Instructions

Delete a W-2, 1099, Schedule C, Schedule E or K-1 record by id. Confirm with the user first.

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": {
      "document_id": "<document_id>"
    },
    "name": "remove_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNo
document_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden; it does disclose the critical trait that this is a destructive removal and gates it behind user confirmation. It stops short of saying whether deletion is permanent, whether it is scoped to a tax year, or what happens when the id is not found, so the safety profile is only partially filled in.

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 with zero filler, and the destructive action plus the qualification list is front-loaded ahead of the confirmation instruction. Nothing repeats the name or title.

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 no explanation, and the description covers the action, the id key, and the confirmation gate. It is only slightly short of complete because tax_year semantics and irreversibility are unaddressed for an irreversible operation with no annotations.

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 0%, so the description must compensate; "by id" does explain document_id's meaning and the enumerated document types clarify what can be removed. The tax_year parameter (default 2026) is never mentioned, leaving the agent to guess whether deletion must be scoped to a year or whether records in other years are unaffected.

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?

States a specific verb (delete) plus the resource by enumerating the concrete document types (W-2, 1099, Schedule C, Schedule E, K-1) and the lookup key (id). An agent can immediately distinguish this from the upsert_* siblings that create or modify the same document types.

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?

Includes one concrete procedural prerequisite, "Confirm with the user first," which is real when-to-use guidance for a destructive operation. However, it gives no exclusions or alternatives, e.g. it does not say whether to use update_other_inputs or an upsert variant to correct a bad record instead of deleting it.

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