Skip to main content
Glama

Mode VC Chart: How Long Does the #1 AI Model Stay on Top?

83(b) Election, QSBS and Delaware Franchise Tax Calculator

calc_83b_qsbs_delaware
Read-onlyIdempotent

Computes the 83(b) filing deadline and tax on the grant, the federal tax saved by a QSBS (Section 1202) exclusion at a given sale price, and Delaware franchise tax under both methods. Federal tax only, top federal rates assumed, no state tax or AMT. Same math as https://modevc.com/tools/83b-qsbs-calculator. Illustrative model, not tax advice.

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

Input Schema

NameRequiredDescriptionDefault
as_of_dateNoDate used for the days-to-deadline count. Defaults to today (UTC).
grant_dateNoDate the shares were transferred, YYYY-MM-DD. Defaults to today.
hold_yearsNoYears the stock is held at sale. Web default 5.
issue_dateNoQSBS stock issue date, YYYY-MM-DD. Defaults to the grant date. Stock issued after 2025-07-04 gets the 50/75/100 percent steps at 3/4/5 years.
de_par_valueNoPar value per share in USD. Web default 0.0001.
fmv_per_shareNoFair market value per share at grant in USD. Web default 0.0001.
shares_grantedNoWeb default 4,000,000.
de_gross_assetsNoGross assets in USD for the assumed par value capital method. Web default 750,000.
de_issued_sharesNoDelaware issued shares. Web default 8,000,000.
exit_stake_valueNoSale value of your stake in USD for the QSBS comparison. Web default 15,000,000.
de_authorized_sharesNoDelaware authorized shares. Web default 10,000,000.
future_fmv_per_shareNoAssumed later fair market value per share, used for the tax a missed 83(b) would cost. Web default 2.50.
price_paid_per_shareNoPrice paid per share in USD. Web default 0.0001.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
provenanceYes
source_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "provenance": {
      +      "properties": {
      +        "as_of": {
      +          "type": "string"
      +        },
      +        "as_of_basis": {
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "as_of",
      +        "as_of_basis",
      +        "sources"
      +      ],
      +      "type": "object"
      +    },
      +    "source_urls": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "provenance"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive behavior, so the description does not repeat those. It adds genuinely useful context beyond them: the assumed rate environment, the exclusion of state tax and AMT, the reference implementation it mirrors, and the not-tax-advice disclaimer.

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 sentences, front-loaded with the three outputs, then the modeling assumptions and disclaimer. No sentence is filler; the URL and disclaimer both carry information an agent needs.

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?

For a 13-parameter, zero-required calculator with a rich schema, an output schema and full safety annotations, the description supplies the assumptions that shape every result. The only minor gap is that it does not characterize what the returned figures look like or how the three computations are separated in the response.

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% and the schema documents every input including defaults and the zero-replacement note, so the burden is already carried. The description adds only loose framing ('a given sale price', 'tax on the grant') and no parameter-level detail beyond the schema, which is the expected baseline.

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 names three concrete computations with specific verbs and resources: the 83(b) filing deadline and grant tax, the QSBS Section 1202 federal tax saved at a sale price, and Delaware franchise tax under both methods. The franchise-tax component is distinguishable from the sibling calc_delaware_incorporation_cost, so an agent can route without opening the schema.

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?

It states the modeling scope (federal tax only, top federal rates, no state tax or AMT) and flags the tool as illustrative rather than tax advice, which implicitly bounds when it applies. However, it never names an alternative or says when to prefer a different calculator for state-tax or incorporation-cost questions.

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.

Resources