AI2Fin (2Fin) Tax MCP

Australian HELP/HECS study-loan repayment

student_loan_repayment

Read-onlyIdempotent

Estimate the compulsory annual study or training loan repayment (HELP, HECS, VSL, SFSS, SSL, AASL) for an Australian resident from their repayment income, using the marginal system introduced in 2025-26 with effective-dated thresholds that roll over each financial year. Use it for "how much HELP/HECS will I repay" questions in AU; it does not cover the loan balance, indexation or voluntary repayments, and applies to Australia only. Repayment income is broader than taxable income — it adds back reportable super contributions, reportable fringe benefits, net investment loss and exempt foreign income; pass that combined figure. Results may include one sourced background fact (relatedFact); the figures do not depend on it.

Input Schema

Name	Required	Description	Default
`taxYear`	No	Financial-year label like '2025-26'; omit to use the current Australian financial year
`repaymentIncome`	Yes	ATO repayment income in AUD (taxable income + reportable super + reportable fringe benefits + net investment loss + exempt foreign income)

Output Schema

Name	Required	Description
`source`	Yes	The national tax authority the figures were verified against (e.g. 'ATO — ato.gov.au')
`country`	Yes	Always AU — this tool is Australia-only
`taxYear`	Yes	Financial year whose thresholds were used
`repayment`	Yes	Compulsory repayment for the year (AUD)
`sourceUrl`	No	https link to the authority page the rate was verified against. Present only on rate answers backed by a verified ledger row — absent (never empty) otherwise, so its presence is itself the claim
`disclaimer`	Yes	General-information note that must accompany any figure shown to a person
`mayBeStale`	Yes	True once the verification date is over a year old — re-confirm with the authority
`relatedFact`	No	One sourced background fact about the country's study-loan repayment; the figures do not depend on it. Absent when no sourced fact fits.
`minThreshold`	Yes	Income at or below which the repayment is nil (AUD)
`effectiveRate`	Yes	repayment ÷ repayment income, as a fraction
`dataVerifiedOn`	Yes	ISO date the rate data was last confirmed against the authority
`repaymentIncome`	Yes	Repayment income used (AUD)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / relatedFact

Added value: +{
+  "additionalProperties": false,
+  "description": "One sourced background fact about the country's study-loan repayment; the figures do not depend on it. Absent when no sourced fact fits.",
+  "properties": {
+    "context": {
+      "description": "Present on a state or provincial answer: the fact is about the country as a whole",
+      "enum": [
+        "national"
+      ],
+      "type": "string"
+    },
+    "country": {
+      "description": "2-letter ISO code of the country the fact is about",
+      "type": "string"
+    },
+    "detail": {
+      "description": "Longer supporting detail, when the corpus has it",
+      "type": "string"
+    },
+    "fact": {
+      "description": "The fact, in one or two sentences",
+      "type": "string"
+    },
+    "kind": {
+      "description": "'origin' = when the tax began and what it replaced; 'anniversary' = the same, on the anniversary of its start date; 'story' = a dated story from the facts corpus",
+      "enum": [
+        "origin",
+        "story",
+        "anniversary"
+      ],
+      "type": "string"
+    },
+    "more": {
+      "description": "The tool that returns the full sourced fact set for this country",
+      "enum": [
+        "tax_facts"
+      ],
+      "type": "string"
+    },
+    "sourceName": {
+      "description": "Who the fact is sourced to",
+      "type": "string"
+    },
+    "sourceUrl": {
+      "description": "Link to that source — always present",
+      "type": "string"
+    },
+    "topic": {
+      "description": "Which tax the fact is about",
+      "enum": [
+        "gst",
+        "income",
+        "company",
+        "cgt",
+        "super",
+        "studentloan",
+        "general"
+      ],
+      "type": "string"
+    },
+    "verifiedDate": {
+      "description": "ISO date the fact was last checked against its source, when recorded",
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "topic",
+    "country",
+    "fact",
+    "sourceName",
+    "sourceUrl",
+    "more"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / sourceUrl

Added value: +{
+  "description": "https link to the authority page the rate was verified against. Present only on rate answers backed by a verified ledger row — absent (never empty) otherwise, so its presence is itself the claim",
+  "type": "string"
+}

AddedJul 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so safety is covered. The description adds real behavioral context beyond that: thresholds are effective-dated and roll over each financial year, a specific income-aggregation rule applies, and results may carry one sourced background fact (relatedFact) that does not affect the figures. Return values need not be described since an output schema exists.

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?

Dense but front-loaded: capability first, then the use case, exclusions, geographic scope, and the input caveat. Nothing is padding, though the parenthetical loan-type list and the repayment-income restatement are slightly repetitive of the schema.

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 two-parameter calculator with full schema coverage, an output schema, and complete annotations, the description leaves no material gap: scope, exclusions, input definition, and the relatedFact caveat are all present.

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 still adds value by hammering that repaymentIncome is broader than taxable income and telling the agent to pass the combined figure — a real disambiguation for the most likely invocation error. It does not go further on taxYear formatting, which the schema already pins down via pattern and examples.

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 (Estimate) plus a precisely scoped resource (compulsory annual HELP/HECS/VSL/SFSS/SSL/AASL repayment) and the method (marginal system, 2025-26 effective-dated thresholds). This is clearly distinguishable from siblings like income_tax_estimate or superannuation_estimate without opening any schema.

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

Usage Guidelines5/5

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

Explicit targeting ("Use it for 'how much HELP/HECS will I repay' questions in AU") plus explicit exclusions (loan balance, indexation, voluntary repayments) and a geographic limitation (Australia only). The agent knows both when to reach for it and when to look elsewhere.

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

All AI2Fin (2Fin) Tax MCP 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.