Skip to main content
Glama

IncredibleFi — Personal Loan Marketplace

submit_loan_application

CONSENT REQUIRED BEFORE CALLING THIS TOOL. Before submitting a loan application, you MUST display the following disclosure to the user verbatim and obtain their explicit agreement (e.g. they say "I agree", "I consent", or "Yes"). Do NOT call this tool until the user has explicitly agreed.

DISCLOSURE: "By submitting this application, you: (1) consent to and agree with IncredibleFi's Terms of Service, Privacy Policy, Credit Authorization Agreement, E-Consent, Arbitration Notice, Advertiser Disclosure, and Personal Loan Notice; (2) certify that all information herein is true and complete; (3) provide written instructions under the Fair Credit Reporting Act for the Marketplace Partners with whom IncredibleFi.com connects you to obtain your consumer credit report from contracted Credit Bureau(s) associated with your pre-qualification for credit inquiry; (4) understand your information will be presented to a network of lenders and/or lending partners who will review and verify your information to determine if you may qualify for a loan, and that lenders and financial service providers may share your personal information including approval and funded status; and (5) provide express consent to recurring communication at the telephone number provided by Acqscale, Inc. (IncredibleFi.com) and its Marketplace Partners. Consent is not required to purchase any goods or services; and (6) understand that if you are not connected with a lender, your information may be shared with, and you may be contacted by, other financial service providers, debt relief providers, aggregators, and marketers offering products that are not loans, and that this consent to be contacted applies to them as well."

Once the user has explicitly agreed, set tcpaConsent to true and submit the application. This tool always returns a URL for the user: either a direct lender match or curated loan options. May return "additional_information_needed" with extra fields to improve matching.

Input Schema

NameRequiredDescriptionDefault
cityYesCity City of your current mailing address.
emailYesEmail address Your email address. Kept private and secure — used to send your loan match results.
phoneYesPhone number 10-digit US mobile or home phone number. Cannot start with 0 or 1.
stateYesState Two-letter US state abbreviation (e.g. CA, TX, NY, FL).
zipCodeYesZIP code 5-digit US ZIP code for your mailing address.
lastNameYesLast name Legal last name — required to verify your identity. 2-30 letters only.
firstNameYesFirst name Legal first name — required to verify your identity. 2-30 letters only.
totalDebtYesTotal outstanding unsecured debt (credit cards, personal loans, medical bills, etc.) — not including mortgage or auto loans. An estimate is fine. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: $20,000 or More, $15,000 - $20,000, $10,000 - $15,000, $5,000 - $10,000, $3,000 - $5,000, $2,000 - $3,000, $1,000 - $2,000, None
loanAmountYesAmount in US dollars between $100 and $40,000. We'll find the best options for you based on this amount. Minimum: $100 Maximum: $40000
creditScoreYesAll credit scores are welcome — including no credit history. This helps us match you with the right lenders. Checking does not impact your score. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Excellent (720+), Good (660-719), Fair (600-659), Poor (Under 600), No credit or not sure
dateOfBirthYesDate of birth Format: YYYY-MM-DD. Must be 18 or older. Required to verify your identity.
loanPurposeYesChoose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Bills, Purchases, Loan Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business
tcpaConsentYesSet to true ONLY after you have displayed the full TCPA/consent disclosure to the user verbatim and the user has explicitly agreed (e.g. said "I agree" or "I consent"). Never set this to true without explicit user agreement.
directDepositYesWhether your income is automatically deposited into your bank account by your employer or benefits provider. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Yes, No
homeOwnershipYesYour current housing situation. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Own, Rent
monthlyIncomeYesYour take-home pay after taxes, per month. An estimate is fine — this helps match you with lenders who fit your income level. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: $10,000 or More, $9,000 - $10,000, $8,000 - $9,000, $7,000 - $8,000, $6,000 - $7,000, $5,000 - $6,000, $4,000 - $5,000, $3,000 - $4,000, $2,500 - $3,000, $2,000 - $2,500, $1,500 - $2,000, Below $1,500
streetAddressYesStreet address Your current US mailing address — for verification only. Example: 123 Main St
employmentStatusYesChoose what best applies. All employment types are accepted including benefits recipients and military. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Employed, Self-employed, Unemployed, Active-duty military
paymentFrequencyYesYour pay schedule — how often income is deposited into your account. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Monthly, Twice a month, Bi-weekly, Weekly
hasCheckingAccountYesA checking account is typically required for loan deposit. Savings accounts do not qualify. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Yes, No
socialSecurityNumberYesSocial Security Number 9-digit SSN with no dashes (e.g. 123456789). For identity verification only — does not impact your credit score. Transmitted with bank-level encryption.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / loanPurpose / description
      Previous value: -"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Bills, Purchases, Debt Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business"New value: +"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Bills, Purchases, Loan Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business"
  2. Changed1 schema field changed
    • changedInput schema / properties / loanPurpose / description
      Previous value: -"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Debt Consolidation, Credit Card Payoff, Emergency Expenses, Major Purchases, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business, Other"New value: +"Choose the option that best describes the primary reason for the loan. Natural language and synonyms are accepted (e.g. \"fair\", \"consolidate debt\", \"biweekly\", \"4500\"). Options: Bills, Purchases, Debt Repayment, Rent or Mortgage, Emergency Expenses, Debt Consolidation, Other, Home Improvement, Education, Travel, Medical Expense, Car Purchase, Business"
  3. Changed2 schema fields changed
    • addedInput schema / properties / tcpaConsent
      Added value: +{
      +  "description": "Set to true ONLY after you have displayed the full TCPA/consent disclosure to the user verbatim and the user has explicitly agreed (e.g. said \"I agree\" or \"I consent\"). Never set this to true without explicit user agreement.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "loanAmount",
      -  "loanPurpose",
      -  "monthlyIncome",
      -  "totalDebt",
      -  "creditScore",
      -  "employmentStatus",
      -  "paymentFrequency",
      -  "streetAddress",
      -  "city",
      -  "state",
      -  "zipCode",
      -  "homeOwnership",
      -  "hasCheckingAccount",
      -  "directDeposit",
      -  "firstName",
      -  "lastName",
      -  "dateOfBirth",
      -  "email",
      -  "phone",
      -  "socialSecurityNumber"
      -]New value: +[
      +  "loanAmount",
      +  "loanPurpose",
      +  "monthlyIncome",
      +  "totalDebt",
      +  "creditScore",
      +  "employmentStatus",
      +  "paymentFrequency",
      +  "streetAddress",
      +  "city",
      +  "state",
      +  "zipCode",
      +  "homeOwnership",
      +  "hasCheckingAccount",
      +  "directDeposit",
      +  "firstName",
      +  "lastName",
      +  "dateOfBirth",
      +  "email",
      +  "phone",
      +  "socialSecurityNumber",
      +  "tcpaConsent"
      +]
  4. First observed

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 does disclose genuinely non-obvious behavior: a hard consent gate, a guaranteed URL return, and an 'additional_information_needed' follow-up path. It does not cover failure modes, duplicate-submission/idempotency behavior, or what happens if tcpaConsent is false, which for a high-stakes write tool leaves gaps.

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 critical instruction and precondition are front-loaded in the first two paragraphs, and the mandated disclosure, while long, is legally required content rather than filler. The nested quoting of the disclosure makes the block slightly awkward to parse, but nothing is truly wasted.

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 21-required-parameter submission tool with no output schema and no annotations, the description covers the highest-risk aspect (consent gating) thoroughly and explains the return shape, so an agent can call it correctly. It is thinner on error handling and re-submission semantics, but the schema covers the parameters fully.

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% across 21 parameters, so the schema already documents each field. The description only elaborates on tcpaConsent, and it largely restates the schema's own tcpaConsent description rather than adding format or validation detail. Baseline 3 applies when the schema does the heavy lifting.

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 operative sentence states a specific verb and resource ('set tcpaConsent to true and submit the application') and describes the return behavior (always a URL; may return 'additional_information_needed'). It is somewhat buried under the compliance boilerplate, and it never names or contrasts the siblings get_loan_application_fields or submit_additional_information, so the agent has to infer the split.

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?

It gives an explicit, unambiguous precondition: display the disclosure verbatim, obtain explicit agreement, and 'Do NOT call this tool until the user has explicitly agreed.' The reference to 'additional_information_needed' implicitly points at the submit_additional_information sibling, but there is no explicit when-not or alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources