Jackpot Calculator MCP

Equal lottery pool shares

calculate_pool_share

Read-onlyIdempotent

Estimate one equal pool member’s cash prize, taxes, and withholding from the total lottery prize, member count, and tax profile.

Instructions

Estimate one equal member’s cash prize, taxes and withholding. Each member is assumed to have the specified tax profile.

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": {
      "prize": "<prize>",
      "members": "<members>",
      "stateCode": "<stateCode>"
    },
    "name": "calculate_pool_share"
  }
}

Input Schema

Name	Required	Description	Default
`game`	No		custom
`prize`	Yes	Whole ticket cash prize in US dollars.
`status`	No		single
`members`	Yes	Equal owners of one ticket. Result assumes every member has the specified tax profile.
`locality`	No	Only valid with stateCode NY.
`stateCode`	Yes	US residence and ticket-purchase state, two-letter code. Cross-state claims are not modeled.
`otherIncome`	No	Other annual income in US dollars before the standard deduction.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read, so the safety profile is covered. The description usefully adds a key modeling assumption (every member is treated as having the same tax profile) and the word 'estimate' signals approximation, but it says nothing about rate limits, precision, or what the 'custom' game mode changes.

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, zero filler, with the per-member scope front-loaded and the shared-tax-profile caveat immediately after. Nothing is repeated and nothing is wasted.

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, the description compensates by naming the returned figures (cash prize, taxes, withholding) and flagging the central simplifying assumption. It is nearly sufficient for a 7-parameter calculator, though the equal-split-only constraint and sibling routing are left implicit.

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 71%, so most parameters are already documented in the schema. The description's only parameter-relevant content restates the members assumption that the schema itself already states, adding no new syntax, defaults, or interaction rules (e.g., locality requiring NY).

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?

States a specific verb (estimate) and a precise resource: one equal member's cash prize, taxes, and withholding. The per-member framing separates it from the single-payout sibling calculate_lottery_payout, though it never names or contrasts that sibling explicitly.

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?

No when-to-use guidance, no exclusions, and no mention of the alternatives calculate_lottery_payout or compare_lump_sum_annuity. The agent must infer from the word 'equal member' that this tool is only for multi-owner pools and not for single winners.

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

Deploy Server