Local Agent Bench

← Leaderboard

mistral:7b

Family: mistral · 7B parameters · 2 run(s)

Why this model scores about 0 on tool selection: what it wrote instead of tool calls, and whether the template, the engine or the model is the cause. Read the analysis. Applies to all runs on this page; scores unchanged.

Fits in 16 GB VRAM · ollama 0.40.6 · Q4_K_M

Measured VRAM at 32K context (KV cache included, ollama ps on the RTX 3090): 8.9 GB · previous tier: 8 GB, rank #11 (results v0.1.1). Moved to the 16 GB tier in results v0.1.2 (2026-10-26) because it needs more than 8 GB at 32K context; score unchanged. Tier rule

22.0/100 · scoring v4

95% task-bootstrap CI (main suite, 3 trials): 19.8–24.2 · pooled over 8 runs (3 main-suite trials + 5 reruns at temperature 0.7): 21.2–25.2 · rank #16 in tier, rank range under weight sensitivity #16–#16 (5th–95th percentile; min #15, max #16) · v3: 22.0 (#14) · mention 0.0% (0/45) · how

Plain-language summary

Doesn't work as a tool-using agent in this suite.

Good for

  • returning clean JSON

Weak at

  • picking the right tool
  • multi-step plans
  • staying safe under prompt injection

Category breakdown

JSON
93
Schema
53
Tool
0
Multi-step
0
Injection useful&safe
0
JSONSchemaToolMulti-stepInjection (useful&safe)tok/sp50 s/taskp95 s/task
9353000128.3 @37becd14.717.7

Prompt injection (15 tasks × 3 trials): useful and safe 0.0% (task completed and not compromised; counts in the score) · utility under attack 0.0% (completed the user's task) · harmful-action attack success 0.0% (a real harmful tool call or canary leak). Mentions (quoting the attacker without acting): 0.0% (0/45); they do not lower the score. v3 useful and safe: 0.0%. v2.1 used injection resistance 100.0 × tool-call rate 0. Definitions

Real 8 GB card: NVIDIA RTX 3070 8 GB (RunPod container) · ollama 0.40.6 · Q4_K_M

Separate series, not part of the tier ranking. 3 single-trial run(s) merged, scoring v4 from the run logs. CPU/GPU split (ollama ps): 8.6 GB 19%/81% CPU/GPU runs with CPU offload (slow) (main tier stays 16 GB) · peak VRAM (nvidia-smi): 6813 MiB of 8192 MiB · series table · how it was measured

21.8/100 · scoring v4

95% task-bootstrap CI: 19.6–23.8 · rank #11 in this series, rank range under weight sensitivity #11–#11 · how

Plain-language summary

Doesn't work as a tool-using agent in this suite.

Good for

  • returning clean JSON

Weak at

  • picking the right tool
  • multi-step plans
  • staying safe under prompt injection

Category breakdown

JSON
91
Schema
55
Tool
0
Multi-step
0
Injection useful&safe
0
JSONSchemaToolMulti-stepInjection (useful&safe)tok/sp50 s/taskp95 s/task
915500021.5 @8fcb65——

Prompt injection (15 tasks × 3 trials): useful and safe 0.0% (task completed and not compromised; counts in the score) · utility under attack 0.0% (completed the user's task) · harmful-action attack success 0.0% (a real harmful tool call or canary leak). Mentions (quoting the attacker without acting): 0.0% (0/45); they do not lower the score. v3 useful and safe: 0.0%. Definitions

Chat template vs upstream

Differs: the GGUF template is not identical to the provider's current upstream template after whitespace normalisation. This is not a safety verdict: older revisions, Ollama conversions and legitimate re-uploads with fixed templates (e.g. Unsloth) often differ.

Labels are only “matches / differs / no reference”, never safe/unsafe. Ollama may use a built-in Go template or renderer instead of the GGUF Jinja. Why templates matter: Chat-template backdoors. Not part of the score.