Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Income Tax Calculator

IncomeTaxCalculator
Read-only

Income Tax Calculator: Income Tax Calculator computes US federal income tax and take-home pay from gross income and filing status. It outputs total tax owed, effective and marginal rates, standard deductions, and net monthly income, and can add Social Security and Medicare (FICA) for true take-home pay. (Cost: 2 credits)

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": {
      "income": "<income>"
    },
    "name": "IncomeTaxCalculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ficaNoInclude the employee share of Social Security and Medicare (FICA) and take-home pay after income tax and FICA. Treats income as one employee's wages.
rateNoTax rate as a percentage (e.g., 22 for 22%)
yearNoThe tax year to use for brackets. Defaults to the previous year.
incomeYesGross annual income in USD
deductionNoOptional deduction amount to subtract from income before calculating tax
filing_statusNoFiling status

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's added value is the scope disclosure (US federal only), the output set, the optional FICA layer that treats income as one employee's wages, and the 2-credit cost. That is meaningful context beyond the annotations, though it says nothing about data vintage or jurisdictional limits beyond 'US federal'.

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

Conciseness4/5

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

The single sentence is front-loaded with the core action and outputs, and the credit cost is appended at the end. It wastes a few words restating the tool name redundantly ('Income Tax Calculator: Income Tax Calculator computes...'), but otherwise no filler.

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 an output schema present, the description need not enumerate return values, and all six parameters are fully documented in the schema. Scope (US federal), FICA behavior, and credit cost are covered; only the unexplained 'rate' parameter and lack of sibling disambiguation keep it from a 5.

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 all six parameters including fica, year, deduction, and filing_status. The description only reinforces income, filing status, and FICA; it adds nothing about the ambiguous 'rate' parameter, which is the one an agent would most likely need clarified.

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 a specific verb and resource — computes US federal income tax and take-home pay from gross income and filing status — and lists the concrete outputs (total tax, effective/marginal rates, deductions, net monthly income). It does not differentiate itself from the sibling IncomeTaxBrackets, which is the closest overlap, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is for estimating US federal income tax and optional take-home pay. There is no explicit statement of when to choose this over IncomeTaxBrackets, SalesTaxCalculator, or payroll-style tools, and no prerequisites or exclusions are given.

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

All APIVerve toolsInspect
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