Papers › m&m's: A Benchmark to Evaluate Tool-Use for multi-step multi-modal Tasks

m&m's: A Benchmark to Evaluate Tool-Use for multi-step multi-modal Tasks

17 Mar 2024arXiv:2403.11085archive 2025-07-28

Zixian Ma, Weikai Huang, Jieyu Zhang, Tanmay Gupta, Ranjay Krishna

Real-world multi-modal problems are rarely solved by a single machine learning model, and often require multi-step computational plans that involve stitching several models. Tool-augmented LLMs hold tremendous promise for automating the generation of such computational plans. However, the lack of standardized benchmarks for evaluating LLMs as planners for multi-step multi-modal tasks has prevented a systematic study of planner design decisions. Should LLMs generate a full plan in a single shot or step-by-step? Should they invoke tools directly with Python code or through structured data formats like JSON? Does feedback improve planning? To answer these questions and more, we introduce m&m's: a benchmark containing 4K+ multi-step multi-modal tasks involving 33 tools that include multi-modal models, (free) public APIs, and image processing modules. For each of these task queries, we provide automatically generated plans using this realistic toolset. We further provide a high-quality subset of 1,565 task plans that are human-verified and correctly executable. With m&m's, we evaluate 10 popular LLMs with 2 planning strategies (multi-step vs. step-by-step planning), 2 plan formats (JSON vs. code), and 3 types of feedback (parsing/verification/execution). Finally, we summarize takeaways from our extensive experiments. Our dataset and code are available on HuggingFace (https://huggingface.co/datasets/zixianma/mnms) and Github (https://github.com/RAIVNLab/mnms).

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 7 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 2 repositories, 9 ran (2 with no instrument failure; 7 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

raivnlab/mnms officialmentioned in papermentioned on GitHubpytorchSyntology: 2 samples, 2 ran (1 instrument-failed) · 0 unverified report
RAIVNLab/mms officialmentioned on GitHubpytorchSyntology: 9 samples, 7 ran (6 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 7 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · violated contract
7ran · our draft was wrong
1ran
2unverified

Licence: 11 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

raivnlab/mnms official repository 2 samples, 2 ran (1 instrument-failed) · 0 unverified
checks_terminate_message mnms/run_plan_agent.py ran · violated contract no licence file found · pointer only · 9c26cc8e53781756 · report fixture: signature msg:dict/0/? · returned bool · level recorded 2026-09-22
read_data_from_file mnms/run_plan_agent.py ran · our draft was wrong no licence file found · pointer only · 5822609079590d9e · report fixture: signature input_file:str/0/str · returned list · level recorded 2026-09-22
RAIVNLab/mms official repository 9 samples, 7 ran (6 instrument-failed) · 2 unverified
find_node_patterns mnms/verifier.py ran · our draft was wrong fingerprinted no licence file found · pointer only · cd95a2581690e761 · report fixture: signature text:str/0/str · returned list · level recorded 2026-09-24
flatten_labels mnms/evaluation/metrics.py ran no licence file found · pointer only · bf0b50da342cb58e · report fixture: signature gt_labels:list/1/str, pred_labels:list/1/str, categories:list/1/str · returned tuple · level recorded 2026-09-24
format_python_str mnms/prompt.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 6bb1d852d31d4d01 · report fixture: signature input_str:str/0/str · returned str · level recorded 2026-09-24
nodes_to_code mnms/evaluation/evaluator.py ran · our draft was wrong no licence file found · pointer only · 1a468c0ba7ba78eb · report fixture: signature nodes:list/1/dict · returned str · level recorded 2026-09-24
nodes_to_program mnms/prompt.py ran · our draft was wrong no licence file found · pointer only · 5e9856951ad7a58e · report fixture: signature nodes:list/1/dict · returned str · level recorded 2026-09-24
object_processing mnms/execution/tool_api.py ran · our draft was wrong no licence file found · pointer only · cd58034ecc1945fe · report fixture: signature file_path:str/0/str · returned dict · level recorded 2026-09-24
replace_node_with_placeholder mnms/evaluation/evaluator.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 76350c7f8fa4a0c6 · report fixture: signature text:str/0/str · returned tuple · level recorded 2026-09-24
find_best_match mnms/evaluation/evaluator.py unverified no licence file found · pointer only · 0776d0fd85848acd · report
get_full_path_data mnms/execution/tool_api.py unverified no licence file found · pointer only · f7710cfb5c0415cb · report

Tasks

4k

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections