What the data for this category looks like
Collateral material data primarily comes from bank credit systems, real estate registration centers, industrial and commercial archive platforms, and paper scans submitted by guarantors. Data updates follow single credit approval cycles, and synchronization occurs when collateral relationships change. Document structures include multiple types of attachments: guarantee letters, guarantor business licenses, real estate mortgage certificates, equity pledge certificates, and more. Core fields include guarantee amount (unit: ten thousand yuan), guarantee period, unified social credit code of the guaranteed entity, collateral appraisal value (unit: yuan), guarantor official seal number, and others. Some attachments are unstructured scan files, which require OCR to extract text content.
What constraints do these characteristics impose on tool calling and plugins
The multi-source and heterogeneous nature of collateral material sources means tool calling must support both structured database field reading and unstructured scan OCR parsing. Plugins must be compatible with cross-system data pulling. The data update feature within a single credit cycle requires that tool calling caches only take effect within a session, to avoid using expired data across sessions. The complex document structure of multiple attachment types requires plugins to support batch file parsing and field association verification, to prevent missing core information. Specific fields and units require tool calling parameters to automatically identify and unify unit formats, to avoid credit review errors caused by unit mismatches. Long document content will also extend the time required for tool calling parsing and parameter generation.
How to Configure Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
UPLOAD_FILE_MAX_SIZE | 200 MB | Collateral materials often include high-definition real estate certificate scans, so single-file size exceeds standard office documents |
PARSE_FILE_TIMEOUT_SECONDS | 1200 seconds | Batch parsing of multiple attachments and OCR processing take significant time, so sufficient processing time must be reserved |
TOOL_CALL_PARAM_SCHEMA | Import custom JSON Schema | Collateral materials have fixed core fields, so field formats and required item requirements must be strictly matched |
TOOL_RETRY_TIMES | 3 times | Cross-system calls or OCR parsing may experience temporary failures, so setting a reasonable number of retries ensures process completion |
OCR_ENABLE | Enabled | Some collateral materials are paper scans, so OCR is required to extract unstructured text content |
MAX_CONTEXT_LENGTH | 8000–12000 characters | Collateral material documents are relatively long, so sufficient context must be retained for tool calling parameter generation |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Configuration Mistakes
- Phenomenon: Plugins cannot be found in the tool calling list after upload. Cause: The plugin file was not placed in the plugin directory specified in the open-source version 4.8.17, or the FastGPT service was not restarted to load the plugin.
- Phenomenon: The
guarantee_amountfield returned by tool calling is empty. Cause: The required field was not configured in the custom Schema, or OCR parsing failed to correctly extract text related to the guarantee amount. - Phenomenon: Tool calling times out with
504 Gateway Timeout. Cause: The setPARSE_FILE_TIMEOUT_SECONDSvalue is less than the actual parsing time, or the number of batch-uploaded collateral materials exceeds the system's single-processing limit.
How to Verify Correct Configuration
- Upload a standard collateral material scan, trigger tool calling, and check whether core fields such as guarantee amount and collateral type can be correctly extracted.
- Enter the plugin management interface, confirm that the custom plugin is displayed in the list of available tools, and that the configured JSON Schema has been successfully loaded.
- Simulate a single credit review scenario, call the tool to batch parse multiple collateral materials, and check whether all parsing is completed within the set timeout period.
- View the tool calling logs, confirm that field formats during parameter transfer match the custom Schema, and that there are no format errors or missing fields.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.