mlsanityData to 13 Oct 2026

Not Every Call Needs a Frontier Model: Per-Call-Site Evaluation of Small Language Models in a Deployed Agentic Home-Automation System

arXiv 2610.09021 ↗First posted 6 Oct 2026cs.AIcited by 0

On the map: LLM agents and tool use → General LLM agent frameworks and benchmarks also fits: Tool learning and function calling

Abstract (arXiv)

An agentic system issues several structurally different kinds of LLM calls. It routes intent, classifies actions, grounds language in a device registry, plans multi-agent pipelines and writes the Python code those pipelines run. The difficulty of these call sites varies by an order of magnitude, yet in practice a single model, chosen for the hardest site, serves all of them. In this work, we evaluate 9 models from 0.8B to a frontier hosted model across the five call sites of a deployed open-source home-automation framework (Wactorz), using its unmodified production prompts and two real Home Assistant installations (280 cases, 2520 scored calls). We find that capability is not ordered the same way at every site, and that larger models are not uniformly better: one 4B model is worse than its 2B sibling at grounded actuation. Paired testing shows the best local model to be statistically indistinguishable from both hosted models at four of five sites. Only code generation separates them, against a small hosted model (p = 0.039) as well as a frontier one (p = 0.002). Aggregate accuracy also hides a safety failure specific to actuation, where small models resolve the accuracy/refusal trade-off in degenerate ways: one model (Gemma4 E2B) actuates on 87.2% of requests for devices the site does not own, while another refuses every request it receives. Routing each site to its best local model reaches 91.8% against 95.4% at no per-call cost. In a live deployment judged by a user, hosting only the two generative sites matches hosting everything (39/43 against 39/43) for 28% of the spend, and the actuation gap the benchmark predicted appears as exactly one case in twenty-six. Benchmark, harness and all records are released at https://github.com/waldiez/slm-callsite-eval.

Key facts. No citing papers in the map yet (data through 13 Oct 2026). Placed in General LLM agent frameworks and benchmarks, one of 16 directions in LLM agents and tool use. Builds on 7 of its 26 references that are in the map. First posted on arXiv 6 Oct 2026.

Builds on

7 of 26 references.

Closest ancestors · 2

Same direction, newest first

  1. 2025Small Language Models are the Future of Agentic AI2 Jun
  2. 2024τ-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains17 Jun

Other references · 5

  1. 2023FrugalGPT: How to Use Large Language Models While Reducing Cost and Improving Performancecited by 815
  2. 2024RouteLLM: Learning to Route LLMs with Preference Datacited by 652
  3. 2026Gemma 4 Technical Reportcited by 229
  4. 2024RouterBench: A Benchmark for Multi-LLM Routing Systemcited by 227
  5. 2024Small Language Models: Survey, Measurements, and Insightscited by 110

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026Characterizing Large Language Model Agentic Workflows: A Study on N8n Ecosystem
  2. 2025Small Language Models for Agentic Systems: A Survey of Architectures, Capabilities, and Deployment Trade offs
  3. 2025LLM-Powered GUI Agents in Phone Automation: Surveying Progress and Prospects
  4. 2025AgentFlux: Decoupled Fine-Tuning & Inference for On-Device Agentic Systems
  5. 2026SMH-Bench: Benchmarking LLM Agents for Environment-Grounded Reasoning and Action in Smart Homes
  6. 2025On-Device LLMs for Home Assistant: Dual Role in Intent Detection and Response Generation
  7. 2024TinyAgent: Function Calling at the Edge
  8. 2026Beyond State Machines: Executing Network Procedures with Agentic Tool-Calling Sequences