What this category of data looks like
Daily documents for this category include mold design task sheets, DFM reports, part drawings, machining process cards, trial mold reports, mold modification notices, and mold records. Data sources include customer product models, mold flow or forming simulations, CAD/CAM, machining and measurement data, and trial mold samples. Updates follow project timelines, with each trial mold or mold modification triggering an update. Document fields include mold number, part tolerances, trial mold defect items, and similar, with units mostly millimeters, seconds, and other standard units. Data formats cover multiple file types including vector drawings, simulation result tables, trial mold photos, and more.
What constraints these characteristics impose on tool calling and plugins workflows
This category has diverse data formats, including vector drawings, tables, images and other file types. Tool calling plugins must support multi-format input and parsing. Update frequency triggers based on project milestones, requiring automatic tool calling to bind to milestones such as trial molds and mold modifications. Extraction of fields related to mold accuracy must be precise. Tool calling must adapt to reading precise values such as millimeter-level tolerances. Fields including project ID and mold number associated with multiple documents must be retained during tool calling to enable traceability of audit processes. The workflow must also support calling external simulation and drawing comparison tools to assist in reviewing forming feasibility issues such as demolding and shrinkage.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Supports automatic tool calling requirements for multi-type documents |
| Workflow/API function-call configuration | Enabled | Supports calling external simulation and drawing parsing tools |
| Image access configuration | Enable HTTP request tool | Supports reading JPG format trial mold photos |
| Timeout setting | 600 seconds | Adapts to the reading and analysis duration of complex mold data |
| Context length | 800–1200 characters | Adapts to the extraction requirements of supporting text for mold drawings |
| Number of recalled results | Top 5 entries | Matches the precise matching scope of core documents under a single project |
Three common misconfigurations
- Issue: JPG images returned by the HTTP request tool cannot be displayed in the conversation interface. Cause: No response format parsing rules for image access are configured, only binary streams are returned without conversion to displayable image links.
- Issue: The AI conversation module cannot directly read uploaded JPG mold drawing files. Cause: The image access configuration for tool calling is not enabled, and the image parsing plugin is not bound.
- Issue: Calling the login interface returns a 401 status code. Cause: The preLogin interface is not called first to obtain a temporary session token, and the formal login interface is called directly.
How to verify the configuration is correct
- Upload a JPG format trial mold photo, and the HTTP request tool returns a previewable image link.
- After enabling
functionCall, external tools can be triggered in conversations to obtain analysis results of mold DFM reports. - After calling the preLogin interface, a valid session token can be obtained for subsequent login interface calls.
- Tool calling logs in FastGPT v4.17.0 can be reviewed, and the project ID and mold number of each call can be recorded, matching the update records of existing mold records.
The values provided are common starting points and should be measured against relevant samples.