AGENT INTELLIGENCE · SOURCE-FIRST
Agent Model Evidence
Model-specific source claims and reported task results, separated from independent measurements.
What is actually documented?
Among 31 Leading and Notable catalog records, 7 unique models have newly reviewed agent-related publisher statements, 7 reported benchmark observations are attributed to model publishers, and 7 runtime-related references are linked. Zero independent agent runtime benchmarks have been run by Open Model Weights. Absence of an entry is unknown, not evidence of failure.
These author-reported numbers come from different tasks, model versions and sometimes incompletely specified harnesses. This table is not a cross-model leaderboard and does not justify normalizing scores or comparing different benchmarks.
ATTRIBUTED NUMBERS
Published agent benchmark observations
Mellum2.1-12B-A2.5B-Thinking: BFCL v4 — evaluation limits
The publisher reports this number; OMW has not run BFCL v4. No comparable result is available here for other curated models.
Macro-average of five BFCL subtasks · Model revision: not pinned to a reproducible run.
Mellum2.1-12B-A2.5B-Thinking: SWE-bench Verified — evaluation limits
This is a vendor evaluation in its specified Pi harness, not an OMW run or a directly transferable deployment result.
Resolved rate reported by JetBrains · Model revision: not pinned to a reproducible run.
Mellum2.1-12B-A2.5B-Thinking: Terminal-Bench 2.1 — evaluation limits
Same author-provided benchmark family; not comparable to other tasks or systems without aligned protocol.
Success rate reported by JetBrains · Model revision: not pinned to a reproducible run.
K2-Horizon-375B-A23B: tau3-Banking — evaluation limits
Model-card table only. Treat metric protocol and exact model revision as unpinned pending deeper verification.
Publisher-reported tau3-Banking result · Model revision: not pinned to a reproducible run.
K2-Horizon-375B-A23B: Toolathlon Verified — evaluation limits
Model-card table only. Do not rank against BFCL or other benchmark versions.
Publisher-reported agentic tool-use result · Model revision: not pinned to a reproducible run.
K2-Horizon-375B-A23B: MCPMark — evaluation limits
Model-card table only; no OMW MCPMark run. Results cannot be pooled across benchmarks.
Publisher-reported MCP tool-use result · Model revision: not pinned to a reproducible run.
Holo4-27B: OSWorld 2.0 — evaluation limits
Not independently rerun by OMW; H Company explicitly notes other leaderboards may use different task subsets/harnesses. Do not treat as a cross-model ranking.
Publisher-reported benchmark success · Model revision: not pinned to a reproducible run.
CAPABILITY EVIDENCE
What publishers say their models can do
Tool calling · Publisher documentation. JetBrains documents tool use and agent training in sandboxed software repositories, plus an exact vLLM tool parser configuration.
Documents design and supported interface, not a reproduced OMW tool-success rate.
Original source ↗
Coding agents · Publisher documentation. JetBrains describes repository, shell and file-editing reinforcement learning and reports software engineering evaluations.
Publisher description and self-reported evaluation; task outcomes depend on the agent harness.
Original source ↗
Tool calling · Publisher documentation. OpenAI documents native function calling, structured outputs and the required Harmony response format for the gpt-oss models.
Supported model behavior is documented; no OMW tool-call accuracy or full agent performance is measured.
Original source ↗
Tool calling · Publisher documentation. Mistral's first-party model card documents native function calling and JSON output and provides a vLLM command with the Mistral tool parser.
Native interface is publisher-documented; cannot infer function-call success on a specific task.
Original source ↗
Agentic tool use · Publisher documentation. The IFM model card publishes its own evaluations on agentic tool-use and long-horizon workflows.
Publisher-reported evaluations; do not convert these scores into verified runtime compatibility or general tool-call guarantees.
Original source ↗
Computer use · Publisher documentation. H Company documents screenshot-guided GUI interaction, code execution and API/MCP tool use via its hai-agents harness.
Official publisher assertion only; OMW did not independently evaluate this checkpoint/harness.
Original source ↗
Tool calling · Publisher documentation. The Holo4-27B publisher documents function calling and tool-driven desktop/browser workflows; exact test success is not independently measured by OMW.
Official publisher assertion only; OMW did not independently evaluate this checkpoint/harness.
Original source ↗
Tool calling · Publisher documentation. IBM Granite 4.2-30B model card documents native tool-calling behavior, reasoning modes and agentic training, with vLLM-compatible API guidance.
Official publisher assertion only; OMW did not independently evaluate this checkpoint/harness.
Original source ↗
Document parsing · Publisher documentation. LightOn documents transcription plus grounding output with region labels, normalized bounding boxes, image descriptions and chart data. It is an ingestion component, not evidence of autonomous agent tool planning.
Official publisher assertion only; OMW did not independently evaluate this checkpoint/harness.
Original source ↗
SERVING INTERFACE
Runtime references are not runtime tests
Mellum2.1-12B-A2.5B-Thinking · vLLMpublisher setup documented
Exact model card command, not executed by OMW. Requires substantial VRAM and version compatibility.
Original source ↗Mistral Small 4 119B A6B · vLLMpublisher setup documented
Publisher's full serving command; not an OMW runtime test. Hardware and installed version must be validated.
Original source ↗gpt-oss-120b · Ollamaruntime catalog documented
Official Ollama library serves its own MXFP4 build; do not equate its artifact hash or memory requirement with the Hugging Face weight file.
Original source ↗GLM-5.3-Flash · llama.cppruntime release documented
Runtime release mentions support. Availability of an exact, validated GGUF checkpoint and tool template is not established.
Original source ↗Holo4-27B · vLLMpublisher setup documented
Hugging Face displays a model serve example. This does not confirm function-call parsing or complete computer-use harness setup; OMW has not run it.
Original source ↗Granite 4.2 30B · vLLMpublisher setup documented
Official Hugging Face serving example; not an OMW-measured end-to-end function-call configuration.
Original source ↗LightOnOCR-3-4B · vLLMpublisher setup documented
Publisher documented with model-specific no-thinking template; do not deploy --trust-remote-code without code review, pinning and sandboxing. No OMW runtime run.
Original source ↗ How to verify the next result
For every numerical agent result, keep the exact model artifact revision, serving runtime and template, benchmark version, evaluation prompts, tool environment, sampling, evaluation code commit and raw outcomes. Without that chain, this site labels results as publisher-reported, never independent.
We provide a bounded localhost-only tool-call smoke-test protocol and a constraint-aware selector. They are not substitutes for a production benchmark.
DIRECT ANSWERS
Questions about this evidence
Are these independent benchmarks?
No. Every numerical result on this page is explicitly attributed to its model publisher; Open Model Weights has not independently reproduced any of them.
Can scores on different benchmarks be compared?
No. BFCL, SWE-bench, Terminal-Bench, tau3, Toolathlon and MCPMark differ in task design, scoring and execution environment.
Does a missing agent benchmark mean a model cannot use tools?
No. Missing model- or version-specific evidence is unknown rather than a negative test.
Sources and verification methods