Skip to main content
Glama

Finology Student Loan Calculator

by tech.finology
OverviewDiscussionsAdmin

estimate_rap_monthly_payment

Estimate the RAP (Repayment Assistance Plan) monthly payment from income, filing status and household size, on the current federal rules. RAP payment only: not a comparison and no forgiveness projection; use the plan comparison tool for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
familySizeNoHousehold size: the borrower, PLUS the spouse when filing jointly, PLUS dependents. 1 = borrower only; a joint filer with two children is 4. RAP's $50 deduction is per QUALIFYING DEPENDENT, which is derived from this and echoed in the response, because a spouse is not a dependent.
annualIncomeYesBorrower's annual adjusted gross income in dollars.
filingStatusNoSingle | MarriedFilingJointly | MarriedFilingSeparately | HeadOfHouseholdSingle
spouseAnnualIncomeNoSpouse's annual AGI, counted only when filing jointly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / dependents
      Removed value: -{
-  "default": 0,
-  "description": "Number of qualifying dependents (IRC 152). A spouse is not a dependent.",
-  "type": "integer"
-}
    • changedInput schema / properties / familySize / description
      Previous value: -"Household size including the borrower."New value: +"Household size: the borrower, PLUS the spouse when filing jointly, PLUS dependents. 1 = borrower only; a joint filer with two children is 4. RAP's $50 deduction is per QUALIFYING DEPENDENT, which is derived from this and echoed in the response, because a spouse is not a dependent."
  2. First observed

TDQS

A4.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 behavioral disclosure burden. It communicates that the tool estimates based on current federal rules and scopes out comparison/forgiveness behavior, but it does not describe the response shape or calculation caveats. Adequate, but not rich.

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 concise sentences with no filler. The first states the purpose and inputs, and the second adds the boundary and alternative tool direction. Every sentence earns its place.

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 single-purpose estimator with fully documented parameters, the description conveys what it computes and what it does not compute, which is enough for correct invocation. It could briefly note the response form since there is no output schema, but that is a minor omission.

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 coverage is 100%, so the baseline is 3. The description's reference to 'income, filing status and household size' adds no meaning beyond what the schema already provides, but no compensation is needed since every parameter is fully documented.

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 uses a specific verb ('Estimate'), identifies the exact resource (RAP monthly payment), and states the inputs that drive the calculation. It also distinguishes itself from sibling comparison tools by explicitly saying it is 'not a comparison and no forgiveness projection.'

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?

The description gives clear when-to-use guidance: this tool is for the RAP payment only, not for plan comparison or forgiveness projection. It even directs the agent to 'use the plan comparison tool for that,' providing an explicit alternative.

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

All Finology Student Loan Calculator toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources