IncredibleFi — Personal Loan Marketplace

submit_additional_information

Submit additional information for a loan application that previously returned "additional_information_needed". Requires the application_reference token from that response.

Input Schema

TableJSON Schema

Name	Required	Description
`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

TDQS

A3.7/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It only mentions the token requirement and the context, but does not describe what happens after submission (e.g., expected response, side effects, whether it finalizes the application). This is a significant gap for a mutation tool.

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 sentences that are direct, informative, and front-loaded with the purpose. No filler or redundancy, earning a top score.

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

Completeness3/5

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

The description covers when to use and what's required, but it does not mention the output or post-submission behavior, and there are no annotations or output schema to fill that gap. It also does not reference the sibling get_loan_application_fields, which could be a relevant prerequisite. Adequate but incomplete.

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?

The input schema has 100% coverage with detailed descriptions for every parameter, including formats, constraints, and examples. The description itself adds no additional parameter-level semantics beyond restating the token requirement, which is already in the schema. Baseline 3 is appropriate.

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 clearly states the action (submit additional information), the resource (a loan application), and the specific condition that triggers this tool (previously returned 'additional_information_needed'). This distinguishes it from siblings like submit_loan_application (initial submission) and get_loan_application_fields (field fetching).

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?

The description provides a clear contextual trigger and a hard prerequisite: it requires the application_reference token from a previous response. However, it does not explicitly state when not to use the tool or mention alternatives, so it stops short of full usage guidance.

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

All IncredibleFi — Personal Loan Marketplace tools Inspect

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.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool serves a distinct role: fetching form fields, submitting additional information, and submitting the loan application. No overlap or ambiguity exists between them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (get_, submit_, submit_). The names clearly indicate the action and target, with no mixed conventions.

Tool Count4/5

With only 3 tools, the set is minimal but still within the ideal 3-15 range. The tools cover the core flow without unnecessary bloat, though it feels slightly thin for a marketplace.

Completeness4/5

The tools cover the full loan application lifecycle: fetching required fields, submitting the application, and handling additional information requests. Minor gaps like status checking are not essential to the described purpose.

Resources

Need Help?