EveryCalc

calculate_fafsa_sai_estimator

Read-onlyIdempotent

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. Use when the user estimates their FAFSA Student Aid Index. 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.

Input Schema

Name	Required	Description
`parent_assets`	Yes	Parent assets in USD.
`parent_income`	Yes	Parent yearly income in USD.
`student_assets`	Yes	Student assets in USD.
`student_income`	Yes	Student yearly income in USD.

Output Schema

Name	Required	Description
`ok`	Yes	True when the calculation succeeded.
`note`	Yes	Disclaimer that accompanies every result.
`tool`	Yes	Name of the tool that ran.
`inputs`	No	The normalized inputs the calculation used.
`results`	Yes	The computed figures for this calculator.
`calculator_url`	Yes	Deep link to the matching interactive calculator on everycalc.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

removedInput schema / properties / household_size

Removed value: -{
-  "description": "Household size, as on the page; the simplified page formula does not use it; default 4.",
-  "type": "number"
-}

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Disclaimer that accompanies every result.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "ok",
-  "tool",
-  "results",
-  "calculator_url"
-]New value: +[
+  "ok",
+  "tool",
+  "results",
+  "calculator_url",
+  "note"
+]

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calculator_url": {
+      "description": "Deep link to the matching interactive calculator on everycalc.xyz.",
+      "type": "string"
+    },
+    "inputs": {
+      "description": "The normalized inputs the calculation used.",
+      "type": "object"
+    },
+    "ok": {
+      "description": "True when the calculation succeeded.",
+      "type": "boolean"
+    },
+    "results": {
+      "description": "The computed figures for this calculator.",
+      "type": "object"
+    },
+    "tool": {
+      "description": "Name of the tool that ran.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "results",
+    "calculator_url"
+  ],
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: the exact calculation constants, the zero floor, and an imperative to surface the result's calculator_url as a clickable markdown link. That post-processing instruction is the kind of behavioral detail no structured field carries. Minor gap: no note on rounding, currency of the constants, or what happens to the result when inputs are zero.

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?

Purpose is front-loaded and the imperative link instruction is clearly marked with IMPORTANT. The formula clause is long and run-on, but every phrase carries information the agent would otherwise have to guess; little could be cut without losing meaning.

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

Completeness5/5

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

For a pure computation tool with an output schema present, the description supplies everything needed: when to invoke it, the formula behind the result, and the required follow-up action with the returned calculator_url. Nothing an agent needs to call or present this tool correctly is missing.

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 the baseline is 3, but the description goes further by explaining how each parameter enters the computation (parent income at 22%, parent assets at 12%, student income above the 11770 allowance at 50%, student assets at 20%). An agent now understands the relative sensitivity of the inputs, which the schema's one-line unit descriptions do not convey.

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?

States a specific verb and resource ("Simplified Student Aid Index estimate") and immediately grounds it in the exact formula used, so an agent can distinguish it from adjacent college-finance siblings like calculate_college_roi or calculate_student_loan_payoff. The domain vocabulary (SAI, Pell Grant, income protection allowance) makes the scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"Use when the user estimates their FAFSA Student Aid Index" gives a clear trigger condition tied to the user's intent. It stops short of naming exclusions or pointing at alternative tools, but among the siblings none overlap enough to create real ambiguity.

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

All EveryCalc 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.