# Tool reference

Source: https://businessloanbroker.ai/agents/tools/
Site: BusinessLoanBroker.ai (powered by Levr)

> Every tool group the business loan MCP exposes, what it reads or writes, and which calls need the owner's confirmation. Submission is the only irreversible action.

Tools are grouped by stage of the application. Reads are safe to call freely. Writes change the application the owner will see. Two actions change lender facing state and need an explicit confirmation from the owner: choosing the lenders and submitting. The live `tools/list` response is always authoritative; this page explains how to use what you will find there.

## Key facts
- **Groups:** Profile, documents, answers, autofill, readiness, matching, selections, submission, status
- **Irreversible:** Submission only
- **Confirmation required:** Lender selection and submission
- **Async tools:** Autofill runs and match runs; poll the get tool until settled

## How should I read the table?

Each row names the stage, the tools you will see for it, whether they read or write, and whether the server expects you to confirm with the owner first. Tool names follow the `resource.action` pattern. Review tools (`review_` prefix) return a description of what a write would do without doing it, which is the right thing to show the owner before an important change.

## What do the application tools return?

`get_contract` returns the fields the application has, their types, which are required, and their current state, so you can plan what to collect instead of guessing. `get_answers` returns current values. `update_answers` accepts a partial object and returns validation results per field. Repeatable items (owners, existing debts, locations) have their own list, add, update and delete tools so you do not have to resend the whole array.

## How does autofill work?

After documents are uploaded, call `prepare_autofill` to see what the server can read from them, then `start_autofill`. Poll `get_autofill` until it settles, then `list_autofill_suggestions`. Each suggestion has the field, the proposed value, the source document and a confidence. Accept the ones that are right with `accept_autofill_suggestion`. Show the owner anything below high confidence before accepting it, especially revenue, existing debt and ownership percentages.

## How do readiness and matching fit together?

Call `check_submission_readiness` before matching. It returns the missing required fields and documents, grouped, with plain language reasons you can relay. Matching (`calculate_matches`) can run on an incomplete file to give the owner an early read, but results firm up once the file is complete. `list_matchmaking_result_summaries` returns each matched lender with the product, a fit label, indicative amounts and the criteria that drove the match, which is what you present to the owner.

## What exactly needs the owner's confirmation?

Two calls. `update_matchmaking_selections`, because it decides which lenders may see the file. And `submit`, because it sends the file. Before each, state in one message: which lenders, what information will be shared, that the owner can stop here, and that approval is not guaranteed. Then call only after a clear yes. The server returns a review payload if you call submit without the confirmation flag, so an accidental call is harmless.

## What comes back after submission?

A deal per lender. `deals.list` and `deals.get` give status and stage. `deals.get_terms` returns offer terms as structured fields (amount, rate or factor, term, payment, fees, conditions) once a lender responds. `deals.list_messages` carries lender questions and stip requests, which you should relay to the owner promptly, since unanswered stips are the most common reason a file stalls.

| Stage | Representative tools | Reads or writes | Needs owner confirmation |
|---|---|---|---|
| Business profile | businesses.get , businesses.update , people.upsert | Read, write | No |
| Documents | client_intake_applications.prepare_answer_file_upload , list_answer_files , get_file_text | Write (uploads), read | No |
| Application answers | client_intake_applications.get_contract , get_answers , update_answers , repeatable item tools | Read, write | No, but show the owner what you changed |
| Autofill from documents | prepare_autofill , start_autofill , list_autofill_suggestions , accept_autofill_suggestion | Write | Show suggestions before accepting |
| Readiness | client_intake_applications.check_submission_readiness | Read | No |
| Lender matching | projects.calculate_matches , get_matchmaking_result , list_matchmaking_result_summaries | Read (computes a match run) | No |
| Choosing lenders | projects.update_matchmaking_selections | Write | Yes. Present the shortlist, get an explicit yes |
| Submission | client_intake_applications.submit , deal_applications.submit | Write, irreversible | Yes, always. Quote what will be sent and to whom |
| Status and offers | deals.list , deals.get , deals.get_terms , deals.list_messages | Read | No |
| Guidance | platform.search_guidance | Read | No |

## Questions and answers
**Are tool names guaranteed stable?**

Within a major version, yes. Deprecated tools keep working for at least 90 days with a description that names the replacement.

**Can I call submit twice by mistake?**

The server protects against duplicate submissions to the same lender. Check deal status before retrying anything, and never show the owner two confirmations for one action.

**Is there a dry run for matching?**

Matching itself is non destructive. Run it as often as the file changes. Only selections and submission touch lender facing state.

## Related
- [End to end workflow for applying on a business's behalf](https://businessloanbroker.ai/agents/workflow/)
- [MCP server for business loan applications](https://businessloanbroker.ai/agents/mcp/)
- [Documents to collect from the owner](https://businessloanbroker.ai/agents/documents/)
- [Security, consent and data handling](https://businessloanbroker.ai/agents/security/)

## Apply
Apply for the business: https://apply.businessloanbroker.ai/signup?utm_source=direct&utm_medium=organic&utm_content=md-agents-tools
MCP server for AI agents: https://mcp.businessloanbroker.ai/mcp (docs: https://businessloanbroker.ai/agents/mcp/)