IncredibleFi — Personal Loan Marketplace
Server Details
AI-powered loan marketplace. Match users with 100+ lenders — any credit score or employment status.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
3 toolsget_loan_application_fieldsAInspect
Get the loan application form fields, their types, allowed values, and validation rules. Call this first to understand what information is needed to submit a loan application.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It compensates by disclosing what data is returned (fields, types, values, rules), but lacks disclosure of other behavioral traits like idempotency, caching behavior, or whether responses vary by user permissions. 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. First sentence establishes capability, second establishes sequencing. Front-loaded action verb and immediately relevant to both the tool's purpose and its relationship to sibling tools.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, description adequately compensates by detailing expected return content (field metadata). Explains relationship to submit_loan_application; minor gap regarding submit_additional_information relationship, but sufficient for tool complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema contains zero parameters. Per rubric, 0 parameters establishes baseline 4. Description appropriately omits parameter explanation since none exist, focusing instead on return value semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Excellent specificity: verb 'Get' + resource 'loan application form fields' + specific attributes 'types, allowed values, and validation rules'. The description clearly distinguishes this from sibling submission tools by focusing on metadata retrieval rather than data submission.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit sequencing instruction: 'Call this first to understand what information is needed to submit a loan application.' This clearly positions the tool as a prerequisite for submit_loan_application, establishing workflow order and preventing premature submission attempts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
submit_additional_informationAInspect
Submit additional information for a loan application that previously returned "additional_information_needed". Requires the application_reference token from that response.
| Name | Required | Description | Default |
|---|---|---|---|
| nextPayDate | Yes | Your next pay date Format: YYYY-MM-DD. The date your next paycheck will be deposited. Must be today or within the next 31 days. | |
| ownsVehicle | Yes | Whether you own a car, truck, or other vehicle — and whether it is paid off or financed. Natural language and synonyms are accepted. Options: Yes - paid off, Yes - making payments, No | |
| employerName | Yes | Employer name Name of your current employer or business. For verification only — your employer will not be contacted. | |
| licenseState | No | State that issued your driver's license Two-letter state abbreviation (e.g. CA, TX). Required if you have a driver's license. | |
| accountNumber | Yes | Bank account number Your checking account number — found on a check or in your banking app. 4-25 digits. Used to deposit funds if matched. | |
| employerPhone | Yes | Employer phone number 10-digit phone number for your employer. For verification only — your employer will not be contacted. | |
| licenseNumber | No | Driver's license number 4-25 alphanumeric characters as printed on your license. Required if you have a driver's license. | |
| routingNumber | Yes | Bank routing number 9-digit ABA routing number for your checking account — found at the bottom left of a check or in your banking app. Used to deposit funds if matched. | |
| hasDriverLicense | Yes | Final identity check — one last step to see your offers. Natural language and synonyms are accepted. Options: Yes, No | |
| application_reference | Yes | Reference token from the previous submit_loan_application response |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It establishes the dependency on previous state but lacks disclosure about idempotency, what happens to existing application data, success/failure behaviors, or rate limits for this financial mutation operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste: first establishes purpose and context, second establishes critical prerequisite. Every word earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (10 parameters, financial domain, workflow dependency), description adequately covers the prerequisite context but could improve by hinting at outcomes (e.g., 'to complete application processing') or noting data sensitivity given no annotations exist.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% description coverage, establishing baseline 3. Description specifically highlights the application_reference token and its origin, adding workflow context, but does not expand on the other 9 parameters which are fully documented in schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Submit' with resource 'additional information' and clearly scopes it to 'loan application that previously returned additional_information_needed', distinguishing it from the initial submit_loan_application tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use: when previous response returned 'additional_information_needed'. Also specifies the required prerequisite (application_reference token from that response), providing clear workflow guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
submit_loan_applicationAInspect
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 Acqscale, Inc and its Marketplace Partners with whom Acqscale, Inc 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. and its Marketing Partners. Consent is not required to purchase any goods or services."
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.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City City of your current mailing address. | |
| Yes | Email address Your email address. Kept private and secure — used to send your loan match results. | ||
| phone | Yes | Phone number 10-digit US mobile or home phone number. Cannot start with 0 or 1. | |
| state | Yes | State Two-letter US state abbreviation (e.g. CA, TX, NY, FL). | |
| zipCode | Yes | ZIP code 5-digit US ZIP code for your mailing address. | |
| lastName | Yes | Last name Legal last name — required to verify your identity. 2-30 letters only. | |
| firstName | Yes | First name Legal first name — required to verify your identity. 2-30 letters only. | |
| totalDebt | Yes | Total 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 | |
| loanAmount | Yes | Amount in US dollars between $100 and $40,000. We'll find the best options for you based on this amount. Minimum: $100 Maximum: $40000 | |
| creditScore | Yes | All 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 | |
| dateOfBirth | Yes | Date of birth Format: YYYY-MM-DD. Must be 18 or older. Required to verify your identity. | |
| loanPurpose | Yes | 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 | |
| tcpaConsent | Yes | 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. | |
| directDeposit | Yes | Whether 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 | |
| homeOwnership | Yes | Your current housing situation. Natural language and synonyms are accepted (e.g. "fair", "consolidate debt", "biweekly", "4500"). Options: Own, Rent | |
| monthlyIncome | Yes | Your 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 | |
| streetAddress | Yes | Street address Your current US mailing address — for verification only. Example: 123 Main St | |
| employmentStatus | Yes | Choose 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 | |
| paymentFrequency | Yes | Your 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 | |
| hasCheckingAccount | Yes | A 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 | |
| socialSecurityNumber | Yes | Social 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. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full disclosure burden. It effectively documents return behavior (always returns URL, may return 'additional_information_needed'), data handling (credit report pulls, lender network sharing), and communication consent implications. Could improve by explicitly stating this creates a permanent application record.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Lengthy due to mandatory legal disclosure text, but appropriately front-loaded with the critical consent warning. Structure logically flows: prerequisites → disclosure text → post-consent actions → return values. Every section serves compliance or operational clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Comprehensive for a high-stakes 21-parameter financial tool. Compensates for missing output schema by describing return values (URL or additional_info flag) and relates to sibling 'submit_additional_information'. Only gap is missing error condition documentation (e.g., what happens if consent is false).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% description coverage (baseline 3). The description adds critical semantic context for tcpaConsent parameter specifically—explaining the exact workflow condition (explicit user agreement required) that schema alone doesn't convey.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool submits a loan application to IncredibleFi/Acqscale, Inc and distinguishes itself from sibling 'submit_additional_information' by being the primary submission entry point versus a follow-up for supplementary data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit prerequisites (user must see disclosure verbatim and explicitly agree), workflow constraints (set tcpaConsent to true ONLY after agreement), and conditions for invocation. Clearly defines the consent gate that must be cleared before calling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!