Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_reference": "<application_reference>",
      "employerName": "<employerName>",
      "employerPhone": "<employerPhone>",
      "nextPayDate": "<nextPayDate>",
      "routingNumber": "<routingNumber>",
      "accountNumber": "<accountNumber>",
      "ownsVehicle": "<ownsVehicle>",
      "hasDriverLicense": "<hasDriverLicense>"
    },
    "name": "submit_additional_information"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextPayDateYesYour next pay date Format: YYYY-MM-DD. The date your next paycheck will be deposited. Must be today or within the next 31 days.
ownsVehicleYesWhether 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
employerNameYesEmployer name Name of your current employer or business. For verification only — your employer will not be contacted.
licenseStateNoState that issued your driver's license Two-letter state abbreviation (e.g. CA, TX). Required if you have a driver's license.
accountNumberYesBank account number Your checking account number — found on a check or in your banking app. 4-25 digits. Used to deposit funds if approved.
employerPhoneYesEmployer phone number 10-digit phone number for your employer. For verification only — your employer will not be contacted.
licenseNumberNoDriver's license number 4-25 alphanumeric characters as printed on your license. Required if you have a driver's license.
routingNumberYesBank 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 approved.
hasDriverLicenseYesFinal identity check — one last step to see your offers. Natural language and synonyms are accepted. Options: Yes, No
application_referenceYesReference token from the previous submit_loan_application response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / accountNumber / description
      Previous value: -"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."New value: +"Bank account number Your checking account number — found on a check or in your banking app. 4-25 digits. Used to deposit funds if approved."
    • changedInput schema / properties / routingNumber / description
      Previous value: -"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."New value: +"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 approved."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the two-step flow and that a reference token from a prior response is mandatory. However, it says nothing about what submission actually does — whether it re-runs verification, triggers a credit check, is final or amendable, or what happens on rejected/invalid data. For a write tool collecting bank, employer, and license data, that is a meaningful gap.

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?

Two sentences, zero filler, with the identifying precondition front-loaded ahead of the token requirement. Nothing is repeated or padded.

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?

For a 10-parameter, 8-required mutation with no annotations and no output schema, the description covers the entry condition and token source but leaves the outcome side unexplained. An agent still cannot tell what a successful call returns or whether the application proceeds automatically, which matters for a terminal-looking submission step.

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% and each of the 10 properties is documented in detail, including formats and conditional requirements (licenseState/licenseNumber required if licensed). The description adds only that application_reference comes from the previous submit_loan_application response, which the schema already states, so baseline 3 applies.

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 description names a specific verb and resource ("Submit additional information for a loan application") and pins the exact precondition: the application previously returned "additional_information_needed". That implicitly separates it from the sibling submit_loan_application (initial submission), though it never names that sibling outright.

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 a clear trigger condition for use — only after a response with status "additional_information_needed" — which is exactly the routing signal an agent needs. It does not state any when-not conditions or what to do if the reference is stale or the status was different.

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