Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Freelance Quarterly Estimated Tax Calculator

estimate_quarterly_tax
Read-onlyIdempotent

Freelance Quarterly Estimated Tax Calculator: OpenChainGraph compute node (consumer_finance). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Open at: https://ainumbers.co/chaingraph/art-752-freelance-quarterly-estimated-tax.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Port of ApexLogics Apex #116 (AL-123) Freelance Quarterly Estimated Tax Calculator into the AINumbers chaingraph shape. Outputs: net_se_income, se_tax, ss_tax, mc_tax, agi, taxable_income, federal_income_tax, effective_fed_rate, state_tax, total_federal_tax, total_annual_tax, effective_total_rate, per_quarter, remaining_after_ytd, safe_harbor_total, safe_harbor_quarterly, quarters, warnings. Output schema: call describe_tool("estimate_quarterly_tax").

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": "estimate_quarterly_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Required: gross_income, business_expenses, other_income, filing_status, state, prior_year_tax, ytd_paid. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds real behavioral context: server-side execution on Cloudflare Workers for gpu:false nodes, browser delegation when compute="browser", transient input processing with no storage or logging, and an AP2 artifact carrying execution_hash for chain provenance. These are traits an agent could not infer from the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is front-loaded with boilerplate ("OpenChainGraph compute node", "Deterministic OpenChainGraph compute node"), then a URL, a 64-character FV-status hash path and a snapshot disclaimer that do nothing to help tool selection. Useful content (privacy, compute modes, outputs) is buried mid-paragraph rather than structured.

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?

Given no output schema, listing the output field names is a genuine aid, and the privacy/compute/provenance notes round out the picture. However, it never explains what the domain outputs mean (e.g. safe_harbor_total, remaining_after_ytd) or how the nested policy inputs drive the result, leaving the agent to call describe_tool for anything substantive.

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 the schema already documents compute, parent_hashes, parent_tool_ids and the nested policy_parameters object. The description echoes the compute-mode semantics already in the schema and adds no meaning about the seven nested policy fields (state, ytd_paid, prior_year_tax, etc.) beyond what the schema states, so baseline 3 applies.

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?

The description names the resource and computation ("Freelance Quarterly Estimated Tax Calculator") and enumerates the concrete outputs (se_tax, ss_tax, safe_harbor_quarterly, per_quarter, etc.), so an agent knows exactly what is produced. It does not differentiate itself from nearby compute nodes such as compute_globe_topup_tax or estimate_iso_amt_exposure, and the opening line largely restates the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this node over the many sibling tax/margin estimators, and no prerequisites or exclusions. The only guidance given is data-handling ("Use synthetic or anonymised inputs only") and compute-mode selection, neither of which tells an agent when this tool is the right call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.