Numeratica — financial planning calculations

tax_qsbs_exclusion

Tax qsbs exclusion. Numeratica POST /v1/tax/qsbs-exclusion — returns JSON with result_id, engine_version, and a not-advice disclaimer (seed echoed for reproducible Monte Carlo where applicable). See the input schema for the accepted fields.

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

Input Schema

Name	Required	Description	Default
`gain`	No
`basis`	No
`tax_year`	No
`other_income`	No
`filing_status`	No
`acquisition_date`	No
`holding_period_years`	No
`gross_assets_at_issuance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

C2.2/5.0

Behavior2/5

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

No annotations are provided, so the description must carry full weight. It discloses the output structure (result_id, engine_version, disclaimer) and notes a reproducible Monte Carlo seed, but fails to mention whether the operation is read-only, destructive, or has authentication/rate-limit requirements.

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

Conciseness3/5

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

The description is short (two sentences) but lacks structure. It front-loads the name but does not clearly separate input, output, or behavior. The instruction to 'See the input schema' is useful but could be more integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 8 parameters, no output schema, and no annotations, the description is insufficient. It does not provide context on how to use the tool effectively, what the parameters mean, or what the return values represent beyond a few fields.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description offers no explanation of any of the 8 parameters (gain, basis, tax_year, etc.), simply deferring to the input schema. This forces the agent to rely solely on parameter names, which may be insufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool is for 'Tax qsbs exclusion' and mentions it returns specific JSON fields, but it doesn't clearly explain what the tool computes or the concept of QSBS exclusion, leaving the purpose somewhat vague. It does distinguish itself from sibling tools by the unique 'qsbs_exclusion' term.

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 guidance on when to use this tool versus alternatives, nor any mention of prerequisites or contexts where it applies. The description only names the tool and its output format.

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

All Numeratica — financial planning calculations 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.