Skip to main content
Search

# Tool calling

5 related articles

Subscribe to updates
  1. OpenRouter Blog

    OpenRouter tests three routes to structured LLM output: 209 of 216 replies met a strict schema, and all 7 misses came from one provider that ignores it

    OpenRouter compared three ways to get reliable JSON out of models, using 24 messy support messages across nine models that support structured outputs: send a strict JSON Schema, force a single tool call, or switch to a decision model that only returns labels. Across the nine models, 209 of 216 replies matched a strict schema, and all 7 misses came from one provider that ignores the schema; asking for JSON only in the prompt produced 18 failures, each from a code fence. For GLM 5.3 FlashX, which only supports tools, forcing the tool call gave 22 valid outputs out of 24, against 0 when the schema was sent directly.

  2. Apple apps get one door to local models: swap the import, keep the session code, and run system or open-weight models

    AnyLanguageModel 1.0 turns Apple's Foundation Models interface into a replaceable layer: an app changes its import from FoundationModels to AnyLanguageModel, and the same session code can call the system model, open-weight models run through llama.cpp, MLX and Core ML, and several hosted providers. Before this, developers curious about local models were unsure how to start and wanted to avoid the added complexity of supporting multiple inference providers. Over the year the library aligned tool calling and guided generation across providers and added image input and Linux support.

  3. Vercel News

    Reflection AI's Beam lands free on AI Gateway: 501B parameters, 23B active per token, built for low latency

    Reflection AI's Beam reasoning model has left stealth testing under the codename stealth/cat-jam and is now available on AI Gateway under its own name, free for a limited launch period when served by Reflection AI. It targets coding and agentic tasks, ships weights under Apache 2.0, supports tool calling and structured outputs, and carries a 1M-token context window. The model has 501B total parameters but activates only 23B per token and skips tokens a task does not need, so it tends to answer sooner than larger open models.

  4. arXiv

    PyRUA-Lean lifts GPT-6 Astra robot agents from 63.1% to 71.7% success under equal call budgets, with 49% fewer calls and 65% fewer input tokens on jointly solved tasks

    PyRUA-Lean is an interactive code-execution framework in which a VLM agent composes classical robot primitives and frozen VLA policies into Python cells that perform conditional checks and local retries and return only explicitly requested images and state feedback; across 700 simulated task instances from LIBERO-PRO, RoboTwin 2.0, and RoboCasa365, and against a tool-calling baseline using the same GPT-6 Astra planner and the same primitives, it raises overall success from 63.1% to 71.7% under equal LLM-call budgets and uses 49% fewer LLM calls and 65% fewer input tokens on instances solved by both agents.

  5. NVIDIA proposes a tool-call-centric agent evaluation framework and uses a SWE-bench trace to show how end-to-end and step-level scoring divide the work

    This NVIDIA article traces how agent evaluation moved from scoring a single function call to scoring whole-task completion, proposes a framework built on an execution environment, two scoring layers (step-level process and end-to-end outcome), and a fixed Benchmark to Trial to Task to Turn to Step hierarchy, and uses a real SWE-bench Verified trace for pytest-dev__pytest-5262 (E2E score 1, step-level 3/4, tool-call precision 3/4, argument accuracy 4/4) to show how each metric should be read, alongside a workflow of setting a public floor and building domain evals from your own tickets and APIs.

You’re all caught up