LABEL CHECK / DOSSIER
Ollama
closure trend: context defaults moved materially across releases (vendor-side, partially closing OL-02); tool-calling deltas show no TD-re-verified closures
Verdict
Ollama's simplicity, model-library, platform, and context-default documentation claims hold as labeled, but its tool-calling label is contradicted where it matters for agents — documented streaming tool support drops tool_calls chunks silently in production, and the get-running-in-minutes agent framing inherits a default context below the vendor's own agentic guidance on common hardware.
Claim ledger — 11 rows
Delta ledger — 6 open
Default context on <24 GiB VRAM hardware (4,096 tokens) is below the vendor's own >=64,000 agentic guidance; truncation remains silent
closes when:Default context on <24 GiB VRAM hardware meets the vendor's own agentic guidance (>=64,000 tokens), or context truncation surfaces an explicit warning or error to the caller — TD re-verified on a current release
evidence:[1][2][3]UPDATE 2026-06-28: v0.30.9 errors on single-message context overflow (partial progress); multi-turn accumulation truncation still silent — delta remains openRe-verified open 2026-06-28 against v0.30.11
Streaming layer returns empty content with finish_reason "stop" in place of tool_calls delta chunks — all tool-dependent agent skills fail silently
Re-checked 2026-06-11: vendor docs now document tool calling with streaming, and the closest upstream issue (#16212) was closed "completed" the same day it was filed after its reporter marked it opened in error. Full detail →
closes when:An agent receives tool_calls delta chunks (correct incrementing indices, finish_reason "tool_calls") over a streaming response in default configuration, with no stream:false workaround — TD re-verified on a current release
evidence:[1][2][3][4][5]Re-verified open 2026-06-28 against v0.30.11
Above ~5-6 active tools, qwen3-coder switches from JSON to XML tool-call format and some models stop attempting tool calls — silent degradation, no error signal
closes when:qwen3-coder emits parseable JSON tool calls (or Ollama's parser transparently normalizes the XML form) with more than 6 active tools, TD re-verified — or the runtime surfaces an explicit signal when a model abandons tool-call formatting
evidence:[1]Re-verified open 2026-06-28 against v0.30.11
`:cloud` tag references route to cloud endpoints without a prior `ollama pull` (v0.18.0) — local-only deployments can route data externally silently
closes when:Referencing a cloud-tagged model from a configuration that has never pulled it requires an explicit opt-in, or fails loudly before any external request is made — TD re-verified
evidence:[1]Re-verified open 2026-06-28 against v0.30.11
Chat template bugs corrupt tool schemas passed via /api/chat before inference — malformed tool definitions upstream of token sampling, unaffected by GBNF enforcement
closes when:Tool schemas pass through /api/chat chat templates intact for the affected models — TD re-verified on a current release
evidence:[1]Re-verified open 2026-06-28 against v0.30.11
Tool parameter literally named "name" is silently dropped (empty content, finish_reason stop) — Mistral-format models, v0.30.10 (#16932)
closes when:A tool whose function schema includes a parameter named 'name' is invoked normally (tool_calls returned) rather than silently dropped, TD re-verified on a current release
evidence:[1]
Closed deltas — 1 (falsification-gated)
Flat low context default (2,048, later 4,096) silently breaking multi-turn tool calling
closed by:v0.6.7 (2025-04-26) raised the default to 4,096; v0.15.5 (2026-02-03) replaced flat defaults with VRAM tiers (4k/32k/256k) — release-reviewed and source-confirmed at HEAD 2026-06-11
Methodology
- sampling
- Label-check methodology (Method §2, D0086) — material-claims rule: a claim is sampled if it appears on the product's own label and would plausibly influence an adoption decision. Sampling frame: ollama.com homepage, the ollama/ollama README, docs.ollama.com capability pages (tool calling, OpenAI compatibility, context length), and release notes v0.6.7-v0.30.7, captured 2026-06-11. The audited product is the local runtime; cloud subscription capacity and pricing claims (Pro/Max tiers) are out of frame. 11 material claims found; all sampled.
- verification depth
- source-reviewed — not executed by Theory Delta
- verification statement
- Evidence is drawn from Ollama's source at HEAD (envconfig/config.go), official docs, release notes, the issue tracker, and a third-party production report; context-length defaults and the streaming-bug issue state were re-checked against source and docs on 2026-06-11 and again on 2026-06-28 (v0.30.11). Theory Delta has not executed Ollama's tool-calling paths in its own environment for this dossier. Star counts (111K+ reported 2026-05-26) are treated as unreliable and excluded from assessment. Decay class: volatile (daily release cadence observed).
- backing confidence
- empirical
- strongest case against
- Ollama ships daily; the streaming tool_calls failure rests on one third-party production report whose closest upstream issue was retracted by its own reporter, and the vendor's docs now document streaming tool calling — TD re-verification could move claim 4 to partial or close OL-03. The context-default delta rests on the vendor's published VRAM tiers; the actual hardware-detection behavior was not executed. The MLX backend switch (March 2026) may have changed streaming behavior on Apple Silicon in either direction.