savi-tools

Tax setaside

get_tax_setaside

Read-only

Estimated annual and quarterly tax to set aside, the IRS safe-harbor minimum, and the next payment due date. Answers "how much should I be setting aside for taxes and when is the next payment due?"

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`basis`	No
`quarters`	Yes
`breakdown`	Yes
`filingStatus`	Yes
`effectiveRate`	Yes
`nextPaymentDue`	Yes
`accountingMethod`	Yes
`quarterlyPayment`	Yes
`safeHarborAnnual`	Yes
`estimatedAnnualTax`	Yes
`safeHarborQuarterly`	Yes
`shouldHaveSavedByNow`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 20, 2026

addedOutput schema / properties / basis

Added value: +{
+  "properties": {
+    "accountingMethod": {
+      "type": "string"
+    },
+    "definitions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "timezone",
+    "definitions"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accountingMethod": {
+      "type": "string"
+    },
+    "breakdown": {
+      "properties": {
+        "federalTax": {
+          "type": "number"
+        },
+        "seTax": {
+          "type": "number"
+        },
+        "stateName": {
+          "type": "string"
+        },
+        "stateTax": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "federalTax",
+        "seTax",
+        "stateTax",
+        "stateName"
+      ],
+      "type": "object"
+    },
+    "effectiveRate": {
+      "type": "number"
+    },
+    "estimatedAnnualTax": {
+      "type": "number"
+    },
+    "filingStatus": {
+      "type": "string"
+    },
+    "nextPaymentDue": {
+      "properties": {
+        "amount": {
+          "type": "number"
+        },
+        "dueDate": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "label",
+        "amount",
+        "dueDate"
+      ],
+      "type": "object"
+    },
+    "quarterlyPayment": {
+      "type": "number"
+    },
+    "quarters": {
+      "items": {
+        "properties": {
+          "amount": {
+            "type": "number"
+          },
+          "dueDate": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "amount",
+          "dueDate"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "safeHarborAnnual": {
+      "type": "number"
+    },
+    "safeHarborQuarterly": {
+      "type": "number"
+    },
+    "shouldHaveSavedByNow": {
+      "type": "number"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "accountingMethod",
+    "estimatedAnnualTax",
+    "quarterlyPayment",
+    "safeHarborAnnual",
+    "safeHarborQuarterly",
+    "shouldHaveSavedByNow",
+    "effectiveRate",
+    "filingStatus",
+    "breakdown",
+    "nextPaymentDue",
+    "quarters"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's safe, non-destructive nature is covered. The description adds no further behavioral context (e.g., data source, update frequency, or potential errors), but given the annotations suffice for safety expectations, a neutral score is appropriate.

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 succinct, using two sentences to convey the outputs and the question it answers. There is no superfluous information, and the structure flows logically from output list to answering a specific user query.

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?

With no output schema provided, the description adequately lists the return items (estimated annual/quarterly amounts, safe-harbor minimum, next payment date) and the question it addresses. It doesn't explain interpretations or edge cases, but for a straightforward read-only tool, this level of detail is sufficient.

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?

The tool has zero parameters, so no parameter descriptions are needed. The baseline of 4 applies, and the description doesn't introduce any ambiguity about parameter usage.

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 the tool provides estimated annual and quarterly tax set-aside amounts, the IRS safe-harbor minimum, and the next payment date, directly answering the question of how much to set aside and when to pay. It is distinct from sibling tools like get_cash_summary or get_expense_summary by focusing specifically on tax obligations.

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 implicitly indicates usage when tax set-aside information is needed, but it does not explicitly contrast with alternatives or state when not to use it. However, given the tool's unique purpose among many financial summary tools, the intended usage is clear enough.

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

All savi-tools 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?