What the data for this category looks like
Traditional Chinese medicine (TCM) marketing content data is primarily sourced from the Pharmacopoeia of the People's Republic of China, internal pharmaceutical company medicinal material processing specifications, clinical practice guidelines, and TCM material traceability systems. Data updates follow the pharmacopoeia's regular revision cycle, with irregular updates from internal pharmaceutical company standards. A single document typically includes these fields: common medicinal material name, Latin name, nature, taste and meridian tropism, functions and indications, usage and dosage, processing method, specification grade, heavy metal and pesticide residue limits. Field units use standard measurements such as grams, milligrams per kilogram, and milliliters. Some fields have format requirements defined by professional terminology.
What constraints do these characteristics impose on tool calling and plugins?
The multi-source, heterogeneous nature of TCM data requires tool calling to support integration with multiple data sources such as pharmacopoeias and internal systems, and to adapt to field format differences across these sources. The long-text structure and specialized field requirements demand precise extraction range specification during tool calling, to avoid irrelevant information being included from overly broad extraction. Strict professional field specifications require plugins to add unit matching and terminology compliance checks during data validation, to prevent professional errors in marketing content. Locally deployed MCP tools must support batch processing of TCM data, to avoid timeouts caused by excessive data volume in a single call.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
tool_call_timeout | 120 seconds | Single TCM marketing document usually contains multiple sections of professional content, requiring sufficient time for extraction and validation |
extract_field_list | ["药材名","性味归经","功能主治","炮制方法","残留限量"] | Matches core display fields for TCM marketing content, avoiding extraction of redundant irrelevant information |
mcp_server_proxy_endpoint | http://localhost:8080 | Standard local connection format for locally deployed MCP Server, compatible with configuration requirements of version 4.96 toolset |
global_var_transfer_mode | header_append | Pass global variables via request headers during external calls, to avoid conflicts with business parameters |
parse_file_max_length | 800–1200 characters | Matches average length of single TCM marketing materials, preventing truncation of key information |
tool_error_retry_count | 2 retries | Addresses occasional format errors during TCM data validation, reducing tool call failure rates |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Mistakes
- When calling a published workflow interface via external means, the global variable field is empty or a parameter validation error is returned. The cause is failure to pass parameters according to the
global_var_transfer_modeconfiguration. Global variables were mistakenly placed in the request body instead of the specified request header or query parameter position. - The text content extraction tool prompts a "field matching failed" error after running. The cause is failure to configure
extract_field_listwith TCM-specific fields. Using a generic field template cannot match the unique professional field structure of TCM documents. - After locally deploying the MCP Server, tool calls return connection timeout or access denied errors. The cause is the absence of an HTTP protocol prefix in
mcp_server_proxy_endpoint. Only enteringlocalhost:portprevents correct resolution of the connection address.
How to confirm the configuration is correctly set
- Call the tool test interface, check if the returned results include all TCM-specific fields preset in
extract_field_list. - Review tool call logs, confirm that the configured value of
mcp_server_proxy_endpointhas been correctly loaded, with no format parsing errors. - Simulate an external call with preset global variable parameters, check if the interface return correctly receives and applies the global variables.
- Adjust the length of the test TCM document, verify that tool calls complete within the time set by
tool_call_timeout, with no timeout or truncation errors.
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.