Skip to main content
Glama

EveryCalc

Server Details

Free finance calculators as MCP tools: mortgage, refinance, loans, compound interest, salary, tips. Every result links the web calculator.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP ยท MCP 2025-03-26
URL

TDQS

Score is being calculated.

Available Tools

69 tools
calculate_401kInspect

Projected 401k balance with employee contributions capped at 24500 per year, plus an employer match, compounded annually. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive 401k calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsYesYears to project.
match_pctYesEmployer match percent of the matched contribution.
annual_salaryYesAnnual salary in USD.
match_cap_pctYesPercent of salary eligible for the employer match.
current_balanceYesCurrent 401k balance in USD.
contribution_pctYesEmployee contribution percent of salary.
annual_return_pctYesAnnual return percent.
calculate_act_scoreInspect

Composite, STEM, and ELA scores from the four ACT section scores, each clamped to 1 to 36 exactly as the page does. The composite is the rounded average of the four sections. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive ACT Score calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
mathYesMath section score, 1 to 36 (clamped and rounded as on the page).
englishYesEnglish section score, 1 to 36 (clamped and rounded as on the page).
readingYesReading section score, 1 to 36 (clamped and rounded as on the page).
scienceYesScience section score, 1 to 36 (clamped and rounded as on the page).
calculate_affordabilityAInspect

Maximum home price affordable from household income using the 28/36 rule. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive home affordability calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
term_yearsNoLoan term in years; default 30.
down_paymentNoCash available for down payment in USD.
annual_incomeYesGross yearly household income in USD.
monthly_debtsNoExisting monthly debt payments in USD.
back_ratio_pctNoBack-end ratio percent; default 36.
annual_rate_pctYesExpected mortgage rate percent.
front_ratio_pctNoFront-end ratio percent; default 28.

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers two useful behavioral facts: the calculation methodology and the fact that the result contains a calculator_url that must be surfaced as a clickable markdown link. It does not disclose what else the result contains or the assumptions behind the price (taxes, insurance, HOA), which is a meaningful gap for an affordability calculation.

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, zero waste. Purpose is front-loaded and the operative instruction about the calculator_url follows immediately, with the IMPORTANT flag making the mandated behavior unmissable.

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 7-parameter calculator with full schema coverage and no output schema, the description covers purpose, method, and the key output element to surface. The remaining gap is the absence of stated assumptions (whether property tax, insurance, or HOA are included in the affordable price), which materially affects interpretation of the result.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns credit by naming the 28/36 rule, which explains the meaning of the front_ratio_pct and back_ratio_pct parameters and their defaults. It also grounds inputs in household income, framing the required annual_income field correctly.

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 and resource: the maximum home price affordable from household income, qualified by the 28/36 rule. This is clearly distinct from calculate_mortgage (payment sizing) and calculate_car_affordability, though the description does not explicitly name a sibling or state the contrast.

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 through the opening purpose statement; there is no explicit when-to-use versus alternatives guidance (e.g., versus calculate_rent_vs_buy or calculate_mortgage). The bolded IMPORTANT instruction is about presenting results, not about selecting this tool over another.

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

calculate_aftInspect

Scores all five AFT events (deadlift, hand-release push-ups, sprint-drag-carry, plank, 2-mile run) from 0 to 100 each using the 17-21 anchor tables, for a 500-point total. Combat MOS scoring is sex-neutral and requires 350 total with every event at 60 or above; the general standard requires every event at 60 or above. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive AFT calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
sexNoSex for the scoring tables (ignored for combat, which is sex-neutral).
push_upsYesHand-release push-up repetitions in 2 minutes.
run_timeYes2-mile run time as m:ss (or total seconds).
standardNoScoring standard: general or combat MOS.
plank_timeYesPlank hold time as m:ss (or total seconds).
deadlift_lbsYes3-rep max deadlift weight in pounds.
sprint_drag_carry_timeYesSprint-drag-carry time as m:ss (or total seconds).
calculate_ageInspect

Exact age from a birth date to a target date, broken into years, months, and days, plus total days lived, total hours lived, the weekday of birth, and days until the next birthday. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive age calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
birth_dateYesDate of birth in YYYY-MM-DD format.
target_dateNoDate to calculate the age as of, in YYYY-MM-DD format. If omitted, today is used, matching the page.
calculate_ap_exam_scoreInspect

Predicted AP score from 1 to 5 using the page bands on the weighted composite percent: multiple choice and free response contributions are weighted by the exam split, then banded at 70, 55, 40, and 25 percent. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive AP Exam Score calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
mc_totalYesTotal multiple choice questions.
frq_totalYesTotal free response points possible.
frq_earnedYesFree response points earned.
mc_correctYesMultiple choice questions answered correctly.
mc_weight_pctNoMultiple choice weight percent for the exam (the page presets are 50, 40, 45, and 60 depending on the exam); default 50.
calculate_arm_vs_fixedInspect

Worst case adjustable rate mortgage simulation with rate caps, compared with a fixed rate loan on total interest, payments, and the breakeven year. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive arm vs fixed calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
term_yearsNoLoan term in years; default 30.
loan_amountYesLoan amount in USD.
fixed_rate_pctYesFixed rate annual percent.
initial_cap_pctYesFirst adjustment cap in percentage points.
lifetime_cap_pctYesLifetime cap above the start rate in percentage points.
periodic_cap_pctYesCap per later adjustment in percentage points.
arm_start_rate_pctYesARM starting annual percent.
fixed_period_yearsYesYears before the ARM first adjusts.
fully_indexed_rate_pctYesFully indexed annual percent the ARM can adjust toward.
calculate_auto_loanInspect

Monthly payment, amount financed, total interest, and total cost of a car for an auto loan after down payment and trade-in value are subtracted from the vehicle price. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive auto loan calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
priceYesVehicle price in USD.
trade_inNoTrade-in value in USD.
term_yearsYesLoan term in years.
down_paymentNoDown payment in USD.
annual_rate_pctYesAnnual rate percent, e.g. 6.5.
include_scheduleNoSet to true to include the yearly amortization schedule.
calculate_bahInspect

Monthly Basic Allowance for Housing from the 2026 RC/Transient baseline rate table by pay grade, with or without dependents, plus the annualized amount. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive BAH calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
pay_gradeYesPay grade, e.g. E-5 or O-3. O-7+ covers O-7 to O-10.
dependentsNoWhether the rate is with or without dependents.
calculate_biweekly_mortgageInspect

Interest and time saved by paying half the monthly mortgage payment every two weeks instead of monthly. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive biweekly mortgage calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
balanceYesCurrent mortgage balance in USD.
term_yearsNoRemaining term in years; default 30.
annual_rate_pctYesAnnual rate percent.
current_monthly_paymentNoCurrent monthly principal and interest payment in USD; leave at 0 to compute it from balance, rate, and term.
calculate_bmi_tdeeInspect

Body mass index and category, Mifflin-St Jeor basal metabolic rate, total daily energy expenditure, and cut and bulk calorie targets. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive bmi and tdee calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
sexNoSex used by the BMR formula: m or f.
age_yearsYesAge in years.
height_cmYesHeight in centimeters.
weight_kgYesWeight in kilograms.
activity_factorNoActivity multiplier, for example 1.2 sedentary, 1.55 moderately active, 1.9 extremely active; default 1.55.
calculate_brs_vs_high3Inspect

Pension-only comparison of the legacy High-3 system (2.5 percent per year of service) against the Blended Retirement System (2.0 percent per year) on the same high-3 average basic pay: monthly, annual, and 30-year lifetime differences. Excludes TSP matching, continuation pay, COLA, and taxes. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive BRS vs High-3 calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
years_of_serviceYesYears of service, clamped by the page to 20 to 40.
high3_monthly_avgYesHigh-3 average monthly basic pay in USD.
calculate_capital_gains_taxInspect

Federal tax on ordinary income plus short term gains at ordinary rates, with long term gains stacked at the 0, 15, and 20 percent thresholds for the filing status. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive capital gains tax calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
filing_statusNoFiling status: single, mfj (married filing jointly), or hoh (head of household).
long_term_gainsYesLong term capital gains in USD.
ordinary_incomeYesOrdinary taxable income in USD, before capital gains.
short_term_gainsNoShort term capital gains in USD; default 0.
calculate_car_affordabilityInspect

Monthly loan payment plus running costs (insurance, fuel, and maintenance, given as annual amounts), total interest, and the five year cost of a car. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive car affordability calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
fuel_annualNoFuel cost per year in USD; default 0.
term_monthsYesLoan term in months.
down_paymentNoDown payment in USD; default 0.
vehicle_priceYesVehicle price in USD.
annual_rate_pctYesLoan annual rate percent.
insurance_annualNoInsurance cost per year in USD; default 0.
maintenance_annualNoMaintenance cost per year in USD; default 0.
calculate_college_acceptanceInspect

Rough acceptance chance: a selectivity tier base rate (92, 80, 50, 20, or 5 percent) adjusted by GPA and test score bands, clamped to 1 to 99 percent and labeled Safety, Target, Reach, or High reach. SAT is used when provided, otherwise ACT. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive College Acceptance calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
actNoACT composite score, used only when no SAT is given, or 0 to leave out; default 0.
gpaYesUnweighted GPA on the 4.0 scale.
satNoSAT total score, or 0 to leave out; default 0.
tier_base_pctNoSelectivity tier base rate percent from the page: 92 open admission, 80 less selective, 50 selective, 20 highly selective, 5 most selective; default 20.
calculate_college_major_roiInspect

Payback years, lifetime earnings minus degree cost, and salary to cost ratio for a major, using the page table of approximate median early career salaries by major. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive College Major ROI calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
majorNoMajor name from the page salary table; default Nursing.
degree_costYesTotal degree cost in USD.
career_yearsNoProjected career years; default 30.
calculate_college_roiInspect

Earnings premium of a degree salary over a no degree baseline salary, both growing at the same annual raise rate, plus the net gain after degree cost, the break-even year, and the return multiple on cost. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive College ROI calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsNoWorking years to project; default 10.
total_costYesTotal degree cost in USD.
baseline_salaryYesStarting yearly salary without the degree in USD.
starting_salaryYesStarting yearly salary with the degree in USD.
annual_raise_pctNoAnnual raise percent applied to both salaries; default 3.
calculate_compound_interestBInspect

Future value of an investment with monthly contributions and monthly compounding. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive compound interest calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsNoProjection horizon; default 30, max 100.
principalNoStarting balance in USD.
annual_rate_pctYesAnnual return percent.
include_scheduleNoInclude the yearly growth schedule.
monthly_contributionNoAdded at the end of each month in USD.

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one genuinely useful behavioral fact: the result contains a calculator_url that should be rendered as a markdown link, which is non-obvious and actionable. However, it says nothing about the shape of the numeric result, the schedule behavior when include_schedule is set, or defaults/limits beyond what the schema already states.

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 with zero filler: the purpose leads, and the output-rendering requirement follows immediately. The IMPORTANT flag correctly draws attention to the one thing an agent could plausibly get wrong.

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?

With no output schema and no annotations, the description is the only place return-value information can live, and it only covers the calculator_url. It omits what the numeric payload looks like and how include_schedule changes the response, which leaves an agent partially blind for a five-parameter financial calculator.

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 every parameter (years, principal, annual_rate_pct, include_schedule, monthly_contribution) is already documented, establishing a baseline of 3. The description's mention of monthly contributions and monthly compounding loosely maps to parameters but adds no syntax, units, or defaults beyond the schema.

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 resource and scope: future value of an investment with monthly contributions and monthly compounding. This distinguishes it from nearby siblings like calculate_roth_conversion or calculate_retirement_savings_planner, though it never explicitly names which sibling to prefer for overlapping retirement/investment questions.

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?

The description contains no when-to-use or when-not-to-use guidance, and no alternatives are mentioned. The only instruction given is about post-processing the result (showing the URL), which is output handling rather than tool-selection guidance.

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

calculate_credit_card_payoffInspect

Months and interest to clear a credit card balance with a fixed monthly payment, compared with adding an extra monthly payment. A payment that never clears the balance returns null months and interest. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive credit card payoff calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
balanceYesCard balance in USD.
extra_paymentNoExtra payment added each month in USD; default 0.
annual_rate_pctYesCard APR percent.
monthly_paymentYesBase monthly payment in USD.
calculate_date_durationInspect

Inclusive number of days between two dates, plus business days after optionally excluding weekends and 2026 US federal holidays, calendar weeks, weekend days, and holidays in the range. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive date duration calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
end_dateYesEnd date in YYYY-MM-DD format.
start_dateYesStart date in YYYY-MM-DD format.
exclude_holidaysNoExclude 2026 US federal holidays from the business day count.
exclude_weekendsNoExclude Saturdays and Sundays from the business day count. The page has this checked by default.
calculate_debt_payoffInspect

Simulates paying off a list of debts month by month with minimum payments plus an extra monthly payment, comparing the avalanche method (highest APR first) with the snowball method (smallest balance first), and reports months to payoff, total interest, payoff order, and the interest and time the avalanche saves. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive debt payoff calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
debt_aprsYesComma-separated annual percentage rates, in the same order as the balances.
debt_namesNoComma-separated debt names, in the same order as the balances, APRs, and minimums. Blank names fall back to Debt 1, Debt 2, and so on.
debt_balancesYesComma-separated debt balances in USD, in the same order as the other debt lists. Debts with a balance of 0 are skipped.
debt_minimumsYesComma-separated minimum monthly payments in USD, in the same order as the balances.
extra_paymentNoExtra payment each month on top of the minimums, in USD.
calculate_dorm_vs_apartmentInspect

Compares the annual dorm cost with an apartment: monthly rent over the number of months, plus annual utilities, extra food cost, and commuting cost. Returns both annual totals, the difference, and which is cheaper. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Dorm vs Apartment calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
monthsNoMonths of rent per year; default 12.
commute_annualYesAnnual commuting cost for the apartment in USD.
dorm_annual_costYesAnnual dorm cost in USD.
utilities_annualYesAnnual utilities cost for the apartment in USD.
food_extra_annualYesAnnual extra food cost versus the dorm meal plan in USD.
apartment_monthly_rentYesMonthly apartment rent in USD.
calculate_emergency_fundInspect

Target emergency fund for a chosen number of months of essential expenses, the remaining gap, percent funded, and months to fill it at a monthly savings rate. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive emergency fund calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
current_savingsNoAlready saved in USD; default 0.
monthly_savingsNoAdded per month in USD; default 0.
monthly_expensesYesEssential monthly expenses in USD.
months_of_coverageNoMonths of expenses to cover, typically 3, 6, 9, or 12; default 6.
calculate_fafsa_sai_estimatorInspect

Simplified Student Aid Index estimate using the page formula: parent income at 22 percent plus parent assets at 12 percent, student income above the 11770 income protection allowance at 50 percent plus student assets at 20 percent, plus an estimated Pell Grant of 7395 minus the SAI, floored at zero. Household size mirrors the page input; the simplified formula does not use it. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive FAFSA SAI Estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
parent_assetsYesParent assets in USD.
parent_incomeYesParent yearly income in USD.
household_sizeNoHousehold size, as on the page; the simplified page formula does not use it; default 4.
student_assetsYesStudent assets in USD.
student_incomeYesStudent yearly income in USD.
calculate_final_examInspect

Score needed on the final exam to reach a desired course grade, with the best and worst possible course grades. Inputs are clamped as on the page: grades to 0 to 100 and the final weight to 1 to 100. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Final Exam calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
final_weight_pctYesFinal exam weight percent of the course grade.
current_grade_pctYesCurrent course grade percent.
desired_grade_pctYesDesired final course grade percent.
calculate_gi_billInspect

Months of the 36-month Post-9/11 GI Bill entitlement remaining, tuition coverage percent, maximum annual books stipend, and Monthly Housing Allowance treatment for the given benefit tier and enrollment level. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive GI Bill calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
tier_pctNoPost-9/11 GI Bill benefit tier percent based on qualifying service.
enrollmentNoEnrollment level: full-time, part-time (over half-time), or half-time or less.
months_usedNoMonths of entitlement already used, 0 to 36.
calculate_gpaInspect

Credit weighted GPA on the 4.0 scale using the page grade points: A+ and A 4.0, A- 3.7, B+ 3.3, B 3.0, B- 2.7, C+ 2.3, C 2.0, C- 1.7, D+ 1.3, D 1.0, F 0.0. Grades and credits are matched by position. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive GPA calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
gradesYesComma-separated letter grades, e.g. A,B+,A-,B.
creditsYesComma-separated credit hours matching grades.
calculate_gpa_plannerInspect

Term GPA required over the planned credits to reach a target cumulative GPA, the maximum reachable cumulative GPA with straight As, and the grade mix the required GPA implies, using the page thresholds. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive GPA Planner calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
target_gpaYesTarget cumulative GPA.
current_gpaYesCurrent cumulative GPA.
current_creditsYesCredit hours already completed.
planned_creditsYesCredit hours planned this term.
calculate_graduate_school_roiInspect

Annual salary premium after a graduate degree, break-even years on the total cost, and lifetime net over the career years, using the page formulas. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Graduate School ROI calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
total_costYesTotal graduate degree cost in USD.
career_yearsNoCareer years after graduation; default 20.
current_salaryYesCurrent yearly salary in USD.
post_degree_salaryYesExpected yearly salary after the degree in USD.
calculate_gre_score_estimatorInspect

Estimated GRE verbal and quant scores on the 130 to 170 scale: 130 plus the fraction of questions correct times 40, per section, plus the total. The optional writing score is clamped to 0 to 6 as on the page. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive GRE Score Estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
quant_totalYesTotal quant questions.
verbal_totalYesTotal verbal questions.
quant_correctYesQuant questions answered correctly.
writing_scoreNoAnalytical writing score, 0 to 6; default 4.
verbal_correctYesVerbal questions answered correctly.
calculate_high_school_course_plannerInspect

Credits still needed per subject against the page requirement table for the selected state (Texas, California, New York, Florida, or Illinois). Remaining per subject is required minus earned, floored at zero. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive High School Course Planner calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
stateNoState code for the requirement table; default TX.
math_creditsYesMath credits earned.
social_creditsYesSocial studies credits earned.
english_creditsYesEnglish credits earned.
science_creditsYesScience credits earned.
electives_creditsYesElective credits earned.
calculate_income_tax_estimatorInspect

Federal income tax after pretax deductions and the standard deduction for the filing status, with AGI, taxable income, marginal rate, and effective rate. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive income tax estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
gross_incomeYesGross annual income in USD.
filing_statusNoFiling status: single, mfj (married filing jointly), or hoh (head of household).
pretax_deductionsNoPretax deductions in USD; default 0.
calculate_inflationInspect

What an amount in today's dollars will buy after a number of years at a given annual inflation rate, what today's basket will cost then, the cumulative price increase percent, and the purchasing power lost. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive inflation calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsNoYears into the future.
amountYesAmount in today's dollars.
annual_rate_pctYesAnnual inflation rate percent, e.g. 3.
include_scheduleNoSet to true to include the purchasing power schedule in 5 year steps (or about 6 steps for longer horizons), matching the page table.
calculate_lease_vs_buyInspect

Lease outlay over the lease term versus buy outlay net of equity in the car at the same point, with the winning option and the net cost difference. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive lease vs buy calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
msrpYesVehicle MSRP in USD.
buy_rate_pctYesBuy loan annual rate percent.
lease_monthsYesLease term in months.
money_factorNoLease money factor, for example 0.0025; default 0.
residual_pctYesResidual value as a percent of MSRP at lease end.
buy_term_monthsYesBuy loan term in months.
buy_down_paymentNoBuy down payment in USD; default 0.
lease_down_paymentNoLease down payment in USD; default 0.
lease_monthly_paymentYesLease monthly payment in USD.
calculate_les_decoderInspect

Net pay from a Leave and Earnings Statement: sums the entitlement lines (base pay, BAH, BAS, other) and deduction lines (federal tax, FICA, state tax, SGLI, TSP, other), and returns net pay plus deductions as a percent of entitlements. Negative line items count as zero, as on the page. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive LES decoder calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
bahNoBAH entitlement in USD.
basNoBAS entitlement in USD.
tspNoTSP deduction in USD.
ficaNoFICA deduction in USD.
sgliNoSGLI deduction in USD.
base_payNoBase pay entitlement in USD.
state_taxNoState tax deduction in USD.
federal_taxNoFederal tax deduction in USD.
other_deductionsNoOther deductions in USD.
other_entitlementsNoOther entitlements in USD.
calculate_loanBInspect

Monthly payment, total interest, and optional amortization schedule for an amortizing loan. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive loan calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
principalYesAmount borrowed in USD.
term_yearsYesTerm in years.
annual_rate_pctYesAnnual rate percent.
include_scheduleNoInclude the yearly amortization schedule.

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, but a pure computation tool has little behavior to disclose. It does add one useful piece of context beyond the schema: the result contains a calculator_url, plus the fact that the schedule is optional and yearly. It does not state that the tool is side-effect-free, nor address rates/units assumptions beyond what the schema implies.

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?

Two sentences: the first front-loads what the tool returns, the second flags a required output-formatting behavior with an IMPORTANT marker. Both earn their place, though the second is an agent-behavior instruction rather than tool semantics.

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?

There is no output schema, so the description must convey return values, and it does list monthly payment, total interest, the optional schedule, and the calculator_url. It stops short of specifying units/precision or edge-case behavior, but for a 4-parameter pure calculator this is close to sufficient.

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 principal, term_years, annual_rate_pct, and include_schedule, establishing a baseline of 3. The description adds only a hint that the schedule is 'yearly' when requested, which is marginally more than the schema's 'Include the yearly amortization schedule'.

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 concrete outputs (monthly payment, total interest, optional amortization schedule) for an amortizing loan, so an agent knows exactly what the tool computes. It does not, however, distinguish this generic amortizing calculator from close siblings such as calculate_mortgage, calculate_auto_loan, or calculate_sba_loan, which are also amortizing-loan calculators.

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 pick this tool over the many sibling loan calculators, nor any stated prerequisites or exclusions. The only instruction present concerns post-call output formatting (showing calculator_url), not tool selection.

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

calculate_lsat_score_estimatorInspect

Estimated LSAT scaled score on the 120 to 180 scale: 120 plus the overall fraction correct across the three sections times 60, with accuracy and the page score band. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive LSAT Score Estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
section1_totalYesTotal section 1 questions.
section2_totalYesTotal section 2 questions.
section3_totalYesTotal section 3 questions.
section1_correctYesSection 1 questions answered correctly.
section2_correctYesSection 2 questions answered correctly.
section3_correctYesSection 3 questions answered correctly.
calculate_mcat_score_estimatorInspect

Estimated MCAT section scores on the 118 to 132 scale: 118 plus the fraction correct times 14, per section, plus the total on the 472 to 528 scale. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive MCAT Score Estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
section1_totalYesTotal section 1 questions.
section2_totalYesTotal section 2 questions.
section3_totalYesTotal section 3 questions.
section4_totalYesTotal section 4 questions.
section1_correctYesSection 1 questions answered correctly.
section2_correctYesSection 2 questions answered correctly.
section3_correctYesSection 3 questions answered correctly.
section4_correctYesSection 4 questions answered correctly.
calculate_military_payInspect

Monthly basic pay from the 2026 pay table for a pay grade and years of service, plus the annualized amount. Grade E1B is the special E-1 rate for the first 4 months of service. Combinations the table does not authorize return authorized=false with null pay. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive military pay calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
pay_gradeYesPay grade. E1B means E-1 with under 4 months of service.
years_of_serviceYesYears of service.
calculate_military_retirement_pensionInspect

Monthly retired pay estimate: years of service times the system multiplier (2.0 percent per year for BRS, 2.5 percent per year for High-3) times the high-3 average monthly basic pay, before taxes, plus annual and 20-year lifetime amounts. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive military retirement pension calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
systemNoRetirement system: brs (2.0 percent per year) or high3 (2.5 percent per year).
years_of_serviceYesYears of service.
high3_monthly_avgYesHigh-3 average monthly basic pay in USD.
calculate_mortgageAInspect

Monthly mortgage payment breakdown: principal and interest via the amortization formula, plus property tax, homeowner insurance, PMI, and HOA. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive mortgage calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
home_priceYesPurchase price in USD.
term_yearsNoLoan term in years; default 30.
hoa_monthlyNoMonthly HOA dues in USD.
pmi_rate_pctNoAnnual PMI rate percent; default 0.5.
annual_rate_pctYesAnnual interest rate percent, e.g. 6.5.
down_payment_pctNoDown payment percent; default 20.
down_payment_usdNoDown payment in USD (wins over down_payment_pct).
include_scheduleNoInclude the yearly amortization schedule.
property_tax_annualNoYearly property tax in USD.
home_insurance_annualNoYearly homeowner insurance in USD.

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose useful non-schema behavior: the amortization-based components included in the monthly breakdown and the requirement to surface calculator_url as a clickable markdown link. It does not explicitly state side-effect or permission behavior, but a mortgage calculator is implicitly non-mutating.

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?

The description is two tight sentences. The first front-loads what is calculated and the second gives an important presentation instruction with no wasted words.

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 10-parameter calculator with no output schema, the description covers the core computation and an important output field behavior. It could go further in describing the result shape or when to request the amortization schedule, but the schema handles parameter details well.

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 10 parameters, including defaults and the down_payment_usd override. The description adds useful context by listing the payment components, but it does not provide parameter-specific semantics beyond what the schema supplies.

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 states a specific calculation: monthly mortgage payment breakdown including principal, interest, property tax, insurance, PMI, and HOA. It is clear what the tool computes, but it does not distinguish itself from nearby siblings such as calculate_loan, calculate_affordability, or calculate_biweekly_mortgage.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, nor does it name alternatives among the many calculator siblings. Usage is only implied by the tool name and the mortgage-specific output.

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

calculate_net_worthInspect

Net worth, total assets, and total liabilities from comma separated asset and liability values, with optional matching names for the largest asset and liability. Only positive values count, as on the page. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive net worth calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
asset_namesNoAsset names, comma separated, in the same order as asset_values.
asset_valuesYesAsset values in USD, comma separated, in the same order as asset_names.
liability_namesNoLiability names, comma separated, in the same order as liability_values.
liability_valuesYesLiability values in USD, comma separated, in the same order as liability_names.
calculate_paycheckInspect

Per paycheck net pay after federal income tax, FICA (Social Security capped at 184500 of wages, Medicare, and the additional Medicare tax), a flat state tax rate, and pretax deductions. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive paycheck calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
annual_salaryYesAnnual salary in USD.
filing_statusNoFiling status: single, mfj (married filing jointly), or hoh (head of household).
pay_frequencyNoPaychecks per year: 52 weekly, 26 biweekly, 24 semimonthly, or 12 monthly; default 26.
pretax_deductionsNoAnnual pretax deductions in USD; default 0.
state_tax_rate_pctYesFlat state tax rate percent, applied to the full salary as on the page.
calculate_pcs_moveInspect

Estimated PCS move money: Dislocation Allowance (DLA) plus Temporary Lodging Expense (TLE, days capped at 21) plus the gross Personally Procured Move (PPM) reimbursement, with the PPM profit after moving costs. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive PCS move calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
dlaNoDislocation Allowance in USD.
ppm_rateNoPPM reimbursement rate per pound in USD.
tle_daysNoTemporary Lodging Expense days, capped at 21.
tle_rateNoDaily TLE rate in USD.
ppm_costsNoActual PPM moving costs in USD.
ppm_weightNoPPM shipment weight in pounds.
calculate_percentageAInspect

Percentage calculations in three modes: percent_of (x percent of y), what_percent (x is what percent of y), percent_change (change from old to new). IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive percentage calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
xNoFor percent_of: the percent. For what_percent: the part.
yNoFor percent_of: the whole. For what_percent: the whole.
newNoFor percent_change: the ending value.
oldNoFor percent_change: the starting value.
modeYesWhich percentage calculation to perform.

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose a non-obvious behavioral fact: the result contains a calculator_url that must be surfaced as a clickable markdown link. Since there is no output schema, this is information the agent could not otherwise obtain. It still omits edge-case behavior (e.g., division by zero when old=0), which keeps it short of a 5.

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 mode definitions are compressed into a single front-loaded sentence, followed by the rendering directive. Every clause carries information, though the capitalized 'IMPORTANT: always show...' sentence is somewhat verbose for a single instruction.

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 five-parameter, single-required-field pure-computation tool with no annotations and no output schema, the description covers the mode semantics and the one notable return value (calculator_url). The main residual gap is edge-case/error behavior, which is minor for a deterministic calculator.

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%: x, y, old, new and the mode enum are each documented in the schema itself, including their per-mode meaning. The description's mode formulas largely restate what the schema already provides, so the baseline of 3 applies.

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 a specific operation (percentage calculation) and enumerates its three distinct modes with plain-language formulas (percent_of, what_percent, percent_change), which immediately separates it from the many domain-specific calculators in the sibling list such as calculate_tip or calculate_capital_gains_tax.

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 explains what each mode computes, which implicitly tells the agent which mode to pick for a given phrasing ("x percent of y" vs "x is what percent of y" vs "change from old to new"). However, it gives no guidance on when to prefer this generic tool over narrower siblings like calculate_tip, and no exclusions or prerequisites.

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

calculate_premed_course_plannerInspect

Progress across the 13 premed prerequisites on the page, in page order: General Chemistry I and II, Organic Chemistry I and II, Biology I and II, Physics I and II, Biochemistry, Psychology, Sociology, Statistics or Calculus, English (1 year). The first 11 are the MCAT core courses. Returns counts done, in progress, and planned, percent done, and whether all core courses are done. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Premed Course Planner calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
statusesYesComma-separated status for each of the 13 prerequisites in page order, each one of not, plan, prog, done, e.g. done,done,not,not,done,done,not,not,not,done,not,not,done.
calculate_property_tax_estimatorInspect

Annual and monthly property tax from the home value minus any exemption, at the given tax rate, with assessed value and effective rate. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive property tax estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
home_valueYesHome value in USD.
tax_rate_pctYesProperty tax rate percent.
exemption_amountNoExemption amount in USD; default 0.
calculate_psat_scoreInspect

Estimated PSAT section scores: 160 plus the fraction correct times 600, using the page fixed totals of 48 questions per section, plus the total and the page percentile band. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive PSAT Score calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
math_correctYesMath questions answered correctly, out of 48.
reading_writing_correctYesReading and writing questions answered correctly, out of 48.
calculate_raise_vs_inflationInspect

Whether a raise beats inflation: nominal new salary, inflation adjusted real salary, the real percent change, and a real raise, real pay cut, or flat verdict. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive raise vs inflation calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
raise_pctYesRaise percent.
inflation_pctYesInflation percent over the same period.
current_salaryYesCurrent salary in USD.
calculate_refinanceBInspect

Refinance break-even month and lifetime savings of refinancing a loan. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive refinance calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
balanceYesCurrent loan balance in USD.
years_leftYesYears remaining on the current loan.
new_rate_pctYesOffered annual rate percent.
closing_costsNoClosing costs in USD.
new_term_yearsNoNew loan term in years; default 30.
current_rate_pctYesCurrent annual rate percent.

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that a calculator_url is returned and implies return fields (break-even month, lifetime savings), which is real added value over the schema. However, it says nothing about modeling assumptions or defaults (e.g., how closing_costs is treated if omitted, or that new_term_years defaults to 30) and does not enumerate the rest of the output.

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?

Two sentences, tightly written, with the core function front-loaded before the output-handling instruction. The 'IMPORTANT' block is somewhat directive in tone but does carry actionable content, so it earns its place rather than padding.

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?

With no output schema, the description is the only place return values can be explained, and it covers only two named outputs plus calculator_url. For a six-parameter calculator with optional inputs, the description leaves the full result shape and default behaviors unstated. It is minimally adequate but has visible gaps.

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 every parameter is already documented in the input schema and the baseline is 3. The description adds no format, unit, or default information beyond what the schema states, so it neither compensates nor detracts.

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-plus-resource pair and enumerates the actual outputs: the refinance break-even month and lifetime savings. That is enough to separate it from siblings like calculate_loan or calculate_mortgage. It stops short of explicitly contrasting itself with close alternatives such as calculate_arm_vs_fixed or calculate_loan.

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 reach for this tool versus the many adjacent loan/mortgage calculators in the sibling list. The only directive is about post-processing the result (rendering calculator_url as a markdown link), which is an output-handling rule, not usage guidance. An agent must infer the use case from the name alone.

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

calculate_rent_vs_buyInspect

Compares the net cost of buying a home (down payment, mortgage payments, tax, insurance, and maintenance, minus principal repaid and appreciation gain) with the total rent paid over the years you plan to stay, and gives a verdict plus the equity built. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive rent vs buy calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
priceYesHome price in USD.
stay_yearsNoYears planning to stay in the home.
term_yearsNoLoan term in years.
monthly_rentYesCurrent monthly rent in USD.
annual_rate_pctYesMortgage annual rate percent, e.g. 6.5.
maintenance_pctNoMaintenance per year as a percent of the home value.
appreciation_pctNoAnnual home appreciation percent.
down_payment_pctNoDown payment percent of the home price.
rent_increase_pctNoAnnual rent increase percent.
property_tax_annualNoProperty tax per year in USD.
home_insurance_annualNoHomeowner insurance per year in USD.
calculate_retirement_savings_plannerInspect

Projected retirement balance from current savings plus monthly contributions with monthly compounding, total contributions, growth, and a 4 percent rule withdrawal figure. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive retirement savings planner calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
current_ageYesCurrent age in years.
retirement_ageYesRetirement age in years.
current_savingsNoCurrent retirement savings in USD; default 0.
annual_return_pctYesAnnual return percent.
monthly_contributionNoMonthly contribution in USD; default 0.
calculate_roth_conversionInspect

Value of converting to a Roth now, with the tax paid out of the converted amount, versus leaving the money in a traditional account taxed at the retirement rate, after growth. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive roth conversion calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsYesYears of growth after conversion.
annual_return_pctYesAnnual return percent.
conversion_amountYesAmount considered for conversion in USD.
current_tax_rate_pctYesTax rate percent if converting now.
retirement_tax_rate_pctYesExpected tax rate percent in retirement.
calculate_roth_vs_traditionalInspect

Compares a Roth and a traditional retirement account at the same pre-tax annual contribution: the Roth invests what is left after tax today and is tax free at withdrawal, the traditional invests the full amount and is taxed at the retirement rate. Reports the winner, both after-tax values, and the tax each side pays. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Roth vs traditional calculator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
ageNoCurrent age in years.
retirement_ageNoRetirement age in years.
annual_return_pctNoExpected annual return percent.
annual_contributionYesAnnual contribution before tax, in USD.
current_tax_rate_pctNoCurrent marginal tax rate percent.
retirement_tax_rate_pctNoExpected tax rate in retirement percent.
calculate_salaryBInspect

Convert between hourly, daily, weekly, biweekly, monthly, and annual pay. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive salary calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
modeNoWhether the input is an hourly rate or an annual salary; default hourly.
annualNoAnnual salary in USD (annual mode).
hourlyNoHourly rate in USD (hourly mode).
hours_per_weekNoHours worked per week; default 40.

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose one genuinely useful behavioral fact: the result contains a calculator_url that should be surfaced to the user โ€” important since there is no output schema. It still omits whether figures are gross or net, rounding, and any assumptions about hours_per_week beyond the schema default.

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?

Two sentences, front-loaded with the capability statement before the imperative instruction. The all-caps IMPORTANT sentence is slightly heavy but earns its place by specifying a required output behavior.

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?

No annotations and no output schema, so the description should compensate more than it does; it hints at calculator_url but never describes the other returned values (the converted amounts). Adequate but with a real gap for an unannotated tool.

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%, including the mode enum default and hours_per_week default, so the schema already documents all four parameters. The description adds no additional parameter meaning; 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?

States a clear verb+resource ('Convert between ... pay') and enumerates the pay periods involved, which distinguishes it from neighbors like calculate_paycheck or calculate_military_pay. However, it claims conversion across six frequencies while the schema only supports hourly<->annual, a mild overstatement that keeps it from 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 Guidelines2/5

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

No when-to-use guidance and no routing away from similar siblings (calculate_paycheck, calculate_military_pay, calculate_biweekly_mortgage). The agent must infer that this is a generic pay-period converter rather than a take-home-pay estimator.

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

calculate_sat_scoreInspect

Estimated SAT section scores: 200 plus the fraction correct times 600, using the page fixed totals of 54 reading and writing questions and 44 math questions, plus the total and the page competitiveness band. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive SAT Score calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
math_correctYesMath questions answered correctly, out of 44.
reading_writing_correctYesReading and writing questions answered correctly, out of 54.
calculate_sba_loanInspect

Monthly payment for an SBA loan with the guarantee fee percent financed into the loan, plus the amount financed, total interest, and total cost. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive sba loan calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
term_yearsYesTerm in years.
loan_amountYesLoan amount in USD.
annual_rate_pctYesAnnual rate percent.
guarantee_fee_pctNoGuarantee fee percent of the loan amount, financed into the loan; default 0.
calculate_scholarship_roi_trackerInspect

Expected value of a scholarship application (award times win probability, clamped to 0 to 100 percent) and its expected value per hour of work, with the page verdict comparing that rate with an hourly wage. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Scholarship ROI Tracker calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
hoursYesHours the application takes.
hourly_wageYesHourly wage of the job the time could go to instead, in USD.
award_amountYesScholarship award amount in USD.
win_probability_pctYesEstimated win probability percent.
calculate_sgli_vs_private_insuranceInspect

Cost comparison of SGLI (0.06 USD per 1,000 USD of coverage per month plus a 1 USD monthly fee) against a private term premium over the given number of years: monthly and total SGLI cost, total private cost, and which is cheaper. The page's age field is not used by its calculation and is not a parameter here. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive SGLI vs private insurance calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsYesComparison horizon in years (minimum 1, as on the page).
coverageYesLife insurance coverage amount in USD.
private_monthlyYesPrivate term insurance monthly premium in USD.
calculate_social_security_estimatorInspect

Primary insurance amount from the bend point formula (1286 and 7749) applied to average indexed monthly earnings, with monthly benefits at ages 62, 67, and 70. Annual earnings, when given above 0, override AIME as annual divided by 12. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive social security estimator calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
aime_monthlyYesAverage indexed monthly earnings in USD.
annual_earningsNoAnnual earnings in USD; when above 0 it overrides aime_monthly. Default 0.
calculate_student_budgetInspect

Monthly budget from job, parent, and aid income against rent, food, books, transport, and fun spending. Returns total income, total expenses, the balance, and the largest category with its share of expenses. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Student Budget calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
funYesMonthly fun and entertainment spending in USD.
foodYesMonthly food spending in USD.
rentYesMonthly rent in USD.
booksYesMonthly books and supplies spending in USD.
transportYesMonthly transport spending in USD.
aid_incomeYesMonthly financial aid income in USD.
job_incomeYesMonthly job income in USD.
parent_contributionYesMonthly contribution from parents in USD.
calculate_student_loan_payoffInspect

Months to pay off a student loan and the total interest, computed month by month exactly as the page does. With an extra monthly payment, also returns the interest and months saved. Returns null fields and never_payoff true when the payment does not cover monthly interest. Payoff dates are not returned because the page derives them from the current date. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Student Loan Payoff calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
apr_pctYesAnnual percentage rate percent.
balanceYesLoan balance in USD.
extra_paymentNoExtra monthly payment in USD; default 100, the page default.
monthly_paymentYesMonthly payment in USD.
calculate_textbook_costInspect

Net cost of buying new, buying used, renting, and digital for a textbook. Purchase options are reduced by the resale value (floored at zero), and the cheapest option is returned. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Textbook Cost calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
rent_priceYesRental price in USD.
resale_valueYesExpected resale value after the term in USD.
buy_new_priceYesPrice to buy the book new in USD.
digital_priceYesDigital edition price in USD.
buy_used_priceYesPrice to buy the book used in USD.
calculate_tipAInspect

Tip amount, bill total, and per-person split. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive tip calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
billYesBill amount in USD.
peopleNoNumber of people; default 1.
tip_pctNoTip percent; default 20.

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does disclose a genuinely non-obvious trait: the result includes a calculator_url that must be rendered as a clickable markdown link. It also implies the shape of the return (tip, total, per-person split), though it says nothing about rounding, negative/zero inputs, or currency conversion.

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?

Two short sentences, front-loaded with what is computed and followed by the critical presentation instruction. No filler, though the opening is a noun fragment rather than a fully formed statement.

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 three-parameter calculator with no output schema and no annotations, the description covers the essentials: what is computed, the fields returned, and the required display behavior for the returned URL. Edge-case behavior (rounding, zero people) is the only meaningful gap.

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 all three parameters including defaults (people=1, tip_pct=20, bill in USD). The description adds nothing about parameter semantics beyond echoing the outputs, so the 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 concrete outputs (tip amount, bill total, per-person split), and the tool name supplies the verb 'calculate'. It is specific enough that an agent knows exactly what it gets back, and no sibling tool covers tip splitting, so differentiation is implicit.

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 when-to-use or when-not-to-use guidance; the only directive concerns how to present the result, not when to invoke the tool. Usage is fairly self-evident from the name, which keeps this from being a 1, but nothing is stated.

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

calculate_transfer_credit_plannerInspect

Credits remaining, terms remaining at the credits taken per term, years remaining at the terms per year, and credits per year. The graduation date label is not returned because the page derives it from the current date. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive Transfer Credit Planner calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
terms_per_yearNoTerms per year; default 2.
credits_per_termYesCredits taken per term.
required_creditsYesTotal credits required for the degree.
completed_creditsYesCredits already completed or transferred.
calculate_tspInspect

Projected TSP balance with annual employee contributions (capped at the 24,500 USD elective deferral limit used by the page) plus, when matching is on, the BRS agency contribution: 1 percent automatic plus a match of 100 percent of the first 3 percent of pay and 50 percent of the next 2 percent. Contributions are treated as annual amounts compounded with the starting balance, as on the page. The page's Roth percent field is not used by its calculation and is not a parameter here. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive TSP calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
yearsYesProjection horizon in years.
salaryYesAnnual salary (basic pay basis) in USD.
balanceNoCurrent TSP balance in USD.
match_onNoWhether BRS agency automatic and matching contributions apply.
return_pctYesAnnual return percent.
contrib_pctYesEmployee contribution percent of salary.
calculate_unit_converterInspect

Converts a value between units in one category: length, weight, temperature, volume, or speed. Returns the converted result in the page's display precision, the value in base units, and the conversion rate (null for temperature, which uses an offset scale). Unit codes must belong to the chosen category. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive unit converter calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
valueYesValue to convert.
to_unitNoUnit code to convert to. Must be a unit of the chosen category, using the same code lists as from_unit.
categoryNoUnit category to convert within.
from_unitNoUnit code to convert from. Must be a unit of the chosen category: length m, km, cm, mi, ft, in; weight kg, g, lb, oz; temperature C, F, K; volume L, mL, gal, floz; speed ms, kmh, mph.
calculate_va_disabilityInspect

Monthly VA disability compensation from the 2026 rates (2.8 percent COLA, effective Dec 1, 2025) for a combined rating from 10 to 100 percent and a dependent status, plus the annualized amount. Dependency add-ons begin at 30 percent. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive VA disability calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
ratingYesVA combined disability rating percent.
dependentsNoDependent status: alone, spouse, spouseChild, spouse2Children, or vetChild.
calculate_word_counterInspect

Counts words, characters, characters excluding whitespace, sentences, and paragraphs in a block of text, plus estimated reading time at 200 words per minute and speaking time at 130 words per minute. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive word counter calculator.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe text to count.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 69 tool updates
    • First observedcalculate_401k
    • First observedcalculate_act_score
    • First observedcalculate_affordability
    • First observedcalculate_aft
    • First observedcalculate_age
    • First observedcalculate_ap_exam_score
    • First observedcalculate_arm_vs_fixed
    • First observedcalculate_auto_loan
    • First observedcalculate_bah
    • First observedcalculate_biweekly_mortgage
    • First observedcalculate_bmi_tdee
    • First observedcalculate_brs_vs_high3
    • First observedcalculate_capital_gains_tax
    • First observedcalculate_car_affordability
    • First observedcalculate_college_acceptance
    • First observedcalculate_college_major_roi
    • First observedcalculate_college_roi
    • First observedcalculate_compound_interest
    • First observedcalculate_credit_card_payoff
    • First observedcalculate_date_duration
    • First observedcalculate_debt_payoff
    • First observedcalculate_dorm_vs_apartment
    • First observedcalculate_emergency_fund
    • First observedcalculate_fafsa_sai_estimator
    • First observedcalculate_final_exam
    • First observedcalculate_gi_bill
    • First observedcalculate_gpa
    • First observedcalculate_gpa_planner
    • First observedcalculate_graduate_school_roi
    • First observedcalculate_gre_score_estimator
    • First observedcalculate_high_school_course_planner
    • First observedcalculate_income_tax_estimator
    • First observedcalculate_inflation
    • First observedcalculate_lease_vs_buy
    • First observedcalculate_les_decoder
    • First observedcalculate_loan
    • First observedcalculate_lsat_score_estimator
    • First observedcalculate_mcat_score_estimator
    • First observedcalculate_military_pay
    • First observedcalculate_military_retirement_pension
    • First observedcalculate_mortgage
    • First observedcalculate_net_worth
    • First observedcalculate_paycheck
    • First observedcalculate_pcs_move
    • First observedcalculate_percentage
    • First observedcalculate_premed_course_planner
    • First observedcalculate_property_tax_estimator
    • First observedcalculate_psat_score
    • First observedcalculate_raise_vs_inflation
    • First observedcalculate_refinance
    • First observedcalculate_rent_vs_buy
    • First observedcalculate_retirement_savings_planner
    • First observedcalculate_roth_conversion
    • First observedcalculate_roth_vs_traditional
    • First observedcalculate_salary
    • First observedcalculate_sat_score
    • First observedcalculate_sba_loan
    • First observedcalculate_scholarship_roi_tracker
    • First observedcalculate_sgli_vs_private_insurance
    • First observedcalculate_social_security_estimator
    • First observedcalculate_student_budget
    • First observedcalculate_student_loan_payoff
    • First observedcalculate_textbook_cost
    • First observedcalculate_tip
    • First observedcalculate_transfer_credit_planner
    • First observedcalculate_tsp
    • First observedcalculate_unit_converter
    • First observedcalculate_va_disability
    • First observedcalculate_word_counter

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
    16
    11 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent โ€” real, source-backed data.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources