Skip to content

Jev directory

Jev Toolspace

A Python research harness evaluating Jev (TypeSafe System One, jev-1.13.0) as a relevance judge for task-level tool spaces. One API call scores every tool with a yes/no noul question per tool, and the repo benchmarks keep-all versus per-request, per-task and trace-based spaces on TGB and BFCL.
Stars
1
Language
Python
Reading time
3 min
Published by
Community
Author
xuan7zhang
Last verified
Oct 2026

Highlights

  • One call scores every tool in a menu: Jev answers a yes/no noul question per tool and returns independent probabilities, so tool scores do not compete.
  • Three settings: A judges every request online, B averages a task's build requests into one space, C judges the executor's build traces.
  • Reported Qwen2.5-7B results: on TGB, Jev-C 80.7 macro accuracy vs 69.5 keep-all; on BFCL multi-turn, Jev-B 17.3 vs 11.3 keep-all and 13.8 Tool2Vec.
  • The client caches calls by the hash of (model, state, questions), throttles to 600 requests per minute, retries 429/529, and JEV_MOCK=1 scores offline.
  • Protocols: TGB is 10 families x (80 build / 320 eval) with a shared K budget; BFCL multi_turn_base is 4 classes x (10 build / 40 test), menus padded to 30.

Quickstart

bash
export JEV_API_KEY=...
JEV_MOCK=1 python -m jev.tgb_run --dir $TGB --tag 7b --conds A,B,C --limit-fit 3 --limit-eval 3 --traces <traces.json> --out-dir /tmp/mock

Watch out

Grounded in the truncated README and GitHub metadata reviewed on 2026-10-15; the README is cut off mid-sentence in the results discussion, the lanes need the external tgb and bfcl_eval packages plus a GPU for executor traces, and the reported numbers come from the project's own runs with a Qwen2.5-7B executor.

Questions about this entry

Short answers drawn from the linked project or page.

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai