PRefine iconLatent Preference Modeling for Multi-Session Personalized Tool Calling

Yejin Yoon*, Minseo Kim*, Taeuk Kim
Hanyang University
Under Review, 2026

*Equal contribution    Corresponding author
PRefine overview figure

No prior session involves flights, so flight_class="Economy" cannot be retrieved from past calls.
The agent must model the user's preference from its cross-function expressions (price_range, free_entry, car_type) and apply it to the unseen argument.

Abstract

Users often omit essential details in their requests to LLM-based agents, resulting in under-specified inputs for tool use. This poses a fundamental challenge for tool-augmented agents, as API execution typically requires complete arguments, highlighting the need for personalized tool calling. To study this problem in a more realistic setup, we present Multi-Session Personalized Tool Calling (MPT), a benchmark comprising 4,695 instances over 459 multi-session interaction histories that cover three challenges: Preference Recall, Induction, and Transfer. We further propose PRefine, a test-time memory method that maintains the user's latent preference as a textual hypothesis revised through a generate–verify–refine loop. Across five LLMs, existing memory systems underperform full-history prompting; PRefine outperforms all baselines and alone surpasses it on Preference Transfer. These results indicate that memory for personalized agents must abstract behavior into preferences, rather than simply archive it.

Overview

Motivation

Personalized tool-using agents must often act on under-specified requests. A query as simple as "Book a flight for my trip" specifies neither the origin, the destination, nor the price. Prior work has largely assumed that user preferences are provided explicitly—as standing instructions, curated profiles, or arguments that appeared earlier in the context—reducing personalized tool calling to a search problem. We argue that user preferences are, in reality, latent, and thus should be inferred rather than retrieved: the cues are mostly implicit in the user's past tool calls.

Research Focus

Consider a user who books a cheap restaurant, tours a free attraction, and rents a compact car—each choice triggering a distinct tool with no shared parameters. To infer that this user favors affordable options, a preference never stated, the agent must generalize across these seemingly unrelated calls. We study whether agents can first model such a latent preference from past behavior, then reason from it to an executable argument value in the target function—a cross-function correspondence rather than a stored-value lookup.

Task RequirementChallenge Dimensions
BenchmarkImplicit
Interaction
Personalized
API Arguments
Preference
Reasoning
Quantified
Interference
NLSI
PTBench
PEToolBench
PrefEval
CUPID
PersonaMem
MPT (ours)
Comparison of personalized interaction benchmarks.
MPT uniquely combines implicit interaction, personalized API arguments, preference reasoning, and quantified interference.

Benchmark: MPT

MPT (Multi-Session Personalized Tool Calling) comprises 4,695 instances over 459 multi-session interaction histories, totaling 6,961 sessions and 95,523 turns (on average, 15.2 sessions per dialogue and 13.7 turns per session), composed from three source corpora (SGD, DuRecDial 2.0, and HomeBench) with five latent preferences realized over 16 function–parameter pairs across 13 functions. Instances split into three reasoning types by how much evidence prior sessions provide for the target argument: Preference Recall (1,375; the argument recurs, so direct reuse suffices), Preference Induction (1,944; a single mention must be corroborated by cross-function evidence), and Preference Transfer (1,376; the argument never occurs and the preference must be generalized to it). Each query comes in context-guided and context-free variants.

MPT construction pipeline
MPT construction: preprocessing, history composition, query construction, and instantiation.
Three reasoning types in MPT
Three reasoning types in MPT: Recall reuses a repeated value, Induction corroborates a single occurrence, and Transfer applies the preference to an argument never instantiated in the history.
PreferenceFunction(parameter = argument)
low_costGetRestaurants(price_range = cheap)
GetRentalCars(car_type = Compact)
GetHotels(average_star = 1,2)
GetRideSharing(shared_ride = True)
GetTravel(free_entry = True)
GetFlights(flight_class = Economy)
high_costGetRentalCars(car_type = Full-size)
GetHotels(average_star = 4,5)
prefers_starGetMovies(starring = ⟨celebrity⟩)
GetMusic(artist = ⟨celebrity⟩)
ecoGetAirConditioner(eco_mode = on)
GetHeating(eco_mode = on)
GetWaterHeater(eco_mode = on)
solo_usageGetBuses(group_size = 1)
GetFlights(passengers = 1)
GetRideSharing(number_of_seats = 1)
GetEvents(number_of_tickets = 1)
GetRestaurants(number_of_seats = 1)
Preference realization in MPT: five latent preferences expressed through 16 function–parameter pairs.
⟨celebrity⟩ ranges over 20 identities mined from DuRecDial 2.0; the preferred identity varies across users.

Method: PRefine

PRefine generate–verify–refine loop
PRefine revises a preference hypothesis η through a generate–verify–refine loop (up to K = 5 rounds);
only verified hypotheses enter memory.

PRefine maintains the estimate of the user's latent preference as a textual hypothesis revised across sessions. After each session, a generator proposes a preference hypothesis from the previous memory and the session's tool calls; a verifier evaluates it against the accumulated history for (1) Evidence Support, (2) Abstraction Quality, (3) Actionability, and (4) Temporal Consistency; rejected candidates are refined with verifier feedback for up to K = 5 rounds. A hypothesis enters memory only after being verified, yielding a memory that is an abstraction of user behavior rather than a raw log.

Verifier behavior during PRefine memory construction
Verifier behavior during memory construction.
Insufficient evidence and over-specificity account for 64.4% of rejections.

Main Results

We evaluate five LLMs (GPT-5, Claude Haiku 4.5, GPT-OSS-20B, Gemma4-12B, and Qwen3-8B) combined with six methods, reporting Overall-F1 along with Explicit-F1 (extracting stated arguments) and Implicit-F1 (completing omitted, preference-sensitive ones). Agents reliably recover explicit arguments but struggle with omitted ones, and performance degrades from Recall through Induction to Transfer. Retrieval- and organization-based memories (RAG, Mem0, LangMem) even fall below full-history prompting on context-free queries, indicating that surfacing past records is not enough unless the evidence is abstracted into a preference. PRefine outperforms all baselines (O-F1 73.57 context-guided / 60.55 context-free; +15.39 / +25.26 over full-history prompting in the five-model macro average) and is the only method to exceed full-history prompting on Preference Transfer.

Context-Guided Query (qcg)Context-Free Query (qcf)
MethodRecallInductionTransferAvg.ΔRecallInductionTransferAvg.Δ
Full-History Prompting64.8563.0046.6758.1749.1939.1617.5135.29
RAG64.7561.0756.9860.93+2.7631.4130.4115.2125.67−9.61
Mem064.6662.4056.3061.12+2.9440.7837.3215.6631.25−4.04
LangMem66.1964.1255.4661.92+3.7544.5542.9616.5134.67−0.61
A-MEM67.8763.5958.4863.31+5.1463.9955.5813.4244.33+9.04
PRefine (Ours)80.5376.1164.0673.57+15.3977.6471.6932.3160.55+25.26
Main results (O-F1, five-model macro average). Δ is relative to Full-History Prompting; bold/underline denote best/second-best.
O-F1, EXP-F1, and IMP-F1 across three reasoning types
O-F1, EXP-F1, and IMP-F1 for context-guided queries across three reasoning types.
EXP-F1 remains high across methods, whereas IMP-F1 declines sharply on Preference Transfer.

Analysis: Evidence Interference

We quantify how hard a history makes preference modeling with a new evidence interference score: each observation is classified as supporting, competing, or unrelated to the target preference, and their weighted ratio stratifies instances by difficulty. All methods degrade as interference increases, but PRefine remains the most robust across all quintiles; isolating competing evidence shows it stays best in every contested subset. Ablations further show that verification—not repeated refinement—drives the gains: unverified refinement degrades below full-history prompting, while the full generate–verify–refine loop peaks at K = 5.

IMP-F1 across interference quintiles
IMP-F1 across evidence-interference quintiles (Q1–Q5).
Performance declines as interference increases; PRefine remains the most robust.
IMP-F1 with and without competing evidence
IMP-F1 with and without competing evidence across Recall, Induction, and Transfer.
PRefine performs best across all three axes.
MethodGenerateVerifyRefineContext-Guided (qcg)Context-Free (qcf)Overall
Full-History Prompting51.9929.6644.82
Generator-only51.1721.5143.81
Generator–RefinerK=150.5314.2942.34
K=349.9011.9641.46
K=550.3713.4342.09
Generator–Verifier–RefinerK=163.7855.7061.47
K=366.0857.3463.49
K=566.4557.9463.95
K=1063.7157.0561.84
Ablation of PRefine (O-F1, averaged over GPT-OSS-20B, Qwen3-8B, and Gemma4-12B).
Generation alone does not beat full-history prompting and unverified refinement degrades further; the verifier drives the gains, peaking at K = 5.

Efficiency

Because PRefine revises a compact preference-level hypothesis rather than accumulating session-level records, it exposes an average of only 26.36 memory tokens per test instance—versus 96.88 for RAG, 121.46 for Mem0, 259.54 for LangMem, and 1,082.58 for A-MEM—and its memory store stays nearly constant as sessions accumulate while the baselines grow continuously. Memory construction costs 8,855.57 tokens per session despite the refinement loop: 6.0% fewer than Mem0 and 67.5% fewer than A-MEM.

MethodLLM Input / SessionEmbedding / SessionOutput / SessionTotal / Session
RAG0.00237.040.00237.04
Mem08,382.97520.57520.579,424.11
LangMem2,088.63343.94343.702,776.27
A-MEM16,354.191,212.509,709.9727,276.66
PRefine8,814.030.0041.548,855.57
Token consumption for memory construction, averaged over all 6,961 sessions.
PRefine (generate–verify–refine, K = 5) costs 6.0% less than Mem0 and 67.5% less than A-MEM.
Test-time memory footprint
Test-time memory context per instance (log scale) and memory growth over sessions;
PRefine keeps both the smallest context and a nearly constant store.

Key Findings

Memory for personalized agents must abstract behavior into preferences, rather than simply archive it. Surfacing past records—whether by retrieval or by organized notes—is not enough; hypotheses refined through verification are what enable cross-function generalization. Transfer under high interference remains challenging, calling for memory methods that better resolve competing evidence and ground inferred preferences in unseen API parameters.

BibTeX

@article{yoon2026latent,
  title = {Latent Preference Modeling for Multi-Session Personalized Tool Calling},
  author = {Yoon, Yejin and Kim, Minseo and Kim, Taeuk},
  journal = {arXiv preprint arXiv:2604.17886},
  year = {2026}
}