Organizations: School of Mathematical Sciences, Beijing University of Posts and Telecommunications, Beijing 100876, China · School of Mathematics and Statistics, Chongqing University, Chongqing 401331, China · School of Science, Beijing Forestry University, Beijing 100083, China
Tool use in LLM systems faces a structural trade-off. Progressive disclosure keeps the prompt small by showing only the tools relevant to the current task, while prompt caching rewards a request prefix that stays fixed across calls; every change to the visible tool list invalidates the cached prefix. This paper treats the trade-off as a problem of request architecture and proposes a dual-path routing design that assigns tool selection and tool delivery to separate channels. The main model always sees a small, fixed set of core tools, so the head of its request is unchanged across calls; all other tools are reached through an independent routing channel, in which a router sub-model searches the full tool list, selects one tool, executes it, and returns the result. Tool registration is automated from source code and supports runtime updates, so the tool set can grow without modifying the main model's request prefix. The design generalizes progressive disclosure: capabilities are disclosed through the routing channel, and the main model's prefix stays stable. A prototype implementation was exercised on 55 functional queries and a 30-turn dialogue; token-level cache hit rates reached 90.99% and 95.2%, cutting input cost to about 12.0% and 8.0% of a no-cache baseline under DeepSeek's pricing, where cache-hit input tokens cost roughly 1/30 of cache-miss tokens.
Figures & tables
Figure 1: Five-layer architecture. Each layer encapsulates complexity downward and provides service abstractions upward; inter-layer communication is entirely based on the MCP protocol or inter-process parameter passing, with no shared internal state.
ID
Rounds
Router
Time (s)
Answer summary
1.1
11
5
150.8
Beijing weather query, saved to file and verified via Router (switched to /tmp sandbox path after path restriction)
1.2
3
0
12.3
rag_project1 retrieved campus, 1 hit
1.3
4
0
23.3
Beijing 31.5°C vs. Shanghai 29.4°C, Beijing hotter
1.4
10
6
115.7
faculty retrieved 0 hits, wrote to file via Router (succeeded after whitelist restriction)
1.5
4
1
26.6
Beijing weather vs. campus retrieval, structured output
Table 1: Experiment 1: Results of multi-step sequential tasks
ID
Rounds
Router
Time (s)
Answer summary
2.1
11
0
25.7
Parallel Beijing/Shanghai weather queries, including humidity and dew point details
2.2
3
0
19.1
Parallel retrieval across two RAG projects (BUPT + Mathematics), both successful
2.3
4
0
17.7
Beijing weather and rag_project1 in parallel
2.4
4
0
25.2
Shanghai weather and rag_project2 in parallel (doctoral retrieval succeeded)
2.5
13
0
68.3
Parallel weather queries for three cities, summarized
Table 2: Experiment 2: Results of parallel tasks
Group
ID
Rounds
Router
Time (s)
Answer summary
A
Q1
4
0
15.7
Beijing weather
A
Q2
3
0
18.2
rag_project1 BUPT retrieval
A
Q3
3
0
11.1
Shanghai weather
A
Q4
3
0
10.1
rag_project2 Mathematics retrieval
A
Q5
3
0
9.3
Guangzhou weather
B
Q1
3
0
14.3
Beijing weather (cold start)
Table 3: Experiment 3: Results of long-chain dialogue