Numerous methodologies have been devised to incorporate multi-agent systems for addressing complex challenges, which are challenging for a singular LLM to resolve. Meta-GPT [1] endeavors to address such intricate challenges by emulating the software development lifecycle. The various departments within a software firm have been transformed into distinct agent roles, each specializing in specific tasks. However, a limitation of the Meta-GPT approach lies in the fact that these agents are defined by human intervention, relying on fixed system prompts and descriptive instructions, which hinders Meta-GPT’s adaptability to novel use cases. Analogous constraints associated with predefined structures are evident in [2], CAMEL (Camel: Communicative Agents for “Mind” Exploration of Large Language Model Society) [3], AGENTVERSE: Facilitating Multi-Agent Collaboration and Exploring Emergent Behaviors [4], and [5]. CAMEL was among the initial endeavors to implement agent role-play for resolving intricate tasks. It demonstrated superior performance in numerous test environments compared to the unrefined LLM model. However, the absence of a feedback loop resulted in discussions deviating from the primary subject matter.

Autogen [6], a multi-agent framework developed by Microsoft, was specifically designed for deployment in multi-agent environments. This framework incorporated various multi-agent principles, including the summarization of previous communications, storage of agents within a database, and simulation of human-to-human interactions in real-world contexts. Despite Autogen’s success in introducing autonomous agents, several limitations were observed. Notably, after the agents’ initial development during the planning phase, no subsequent refinement was conducted. As a result, agents often became redundant, and superfluous agents were created that did not address the necessary tasks, causing discussions to deviate into irrelevant topics.

The “Autoagents” [6] paper addressed some of the limitations inherent in the “autogen” paper regarding agent creation by integrating a critic agent within the planning phase. This integration facilitated the inclusion of only the necessary agents during the planning process, thereby reducing the overhead associated with excessive inter-agent communication. However, a limitation of this framework is that the backend Language Learning Model (LLM) used for tasks remains static and predefined from the outset. In some respects, this architecture could be emulated through the use of a reasoning LLM in conjunction with a critic agent or evaluator within a loop. Multi-agent collaboration is most effective when each agent is highly specialized within its domain, as observed in real-world scenarios. Although the evaluator participates in the planning stage, its role is not sufficiently effective in reducing the number of agents or optimizing system prompts such that fewer agents could manage tasks typically requiring many. Furthermore, once an agent is created, this framework cannot alter the agent’s characteristics.

EvoAgents [7] utilized evolutionary methodologies for agent creation. The framework of evolutionary agents effectively addressed issues of redundancy among agents in the planning phase by introducing these agents. Once developed, the agents undergo an evolutionary process whereby redundant agents are eliminated, and a new collection of agents is generated with refined prompts. The research primarily concentrated on the planning phase, notably lacking an evaluator during the execution stages. This absence is problematic, as even the most optimized set of agents cannot guarantee error-free outcomes.

MindSearch [8] emulates human reasoning by employing a network of nodes operated by Large Language Model (LLM) agents. Upon receiving an inquiry from a user, it conducts a search and ceases further action if the result is obtained. Should the answer remain elusive, the system diverges into multiple nodes, each probing in distinct directions. In comparative evaluations, it demonstrates significant performance advantages over prominent search frameworks. However, it is limited by its inability to integrate multiple agents and lacks the capacity to modify the LLM engine’s backend to suit varying search requirements. Furthermore, it does not exhibit adaptability to programming-related tasks.

Agentic Reasoning [9] utilizes mind mapping and agentic reasoning models applied to the GPQA [10] dataset. Their findings suggest that employing basic tools, such as web browsers and Python interpreters, alongside mind maps fortified with agentic reasoning, can produce superior outcomes compared to those of human experts. The research asserts that the resolution of complex problems does not necessitate reliance on intricate agents; rather, the synergy of simple tools with reasoning models can effectively manage most tasks. Nonetheless, this methodology presents certain limitations, principally its dependence on a singular model throughout the process. By integrating an array of models, a diverse set of experts can be engaged for specific tasks. Furthermore, utilizing a variety of foundational models helps to diminish bias and reduce instances of hallucinations in the model’s outputs, as these models are developed using significantly varied datasets and hyperparameters.

Below is the comparison of capabilities for AMASS vs the other multi agent systems. AMASS has more diverse set of capabilities (Table 1).

Table 1. Comparison of previous work.

Continued

The architecture comprises four principal componentsFigure 1: the Preprocessor, the Planner, the Executor, and the Summarizer. The Preprocessor is tasked with processing images and videos while integrating the necessary context into the user’s query. The Planner is dedicated to devising a final set of optimal agents along with a comprehensive plan tailored to accomplish the user’s objective. The Executor employs these agents and the formulated plans to produce the desired outcomes, including executing code, conducting internet searches, and facilitating discussions among various agents. Lastly, the Summarizer interprets the entirety of the dialogue and, in response to the user’s question, delivers a precise answer.

Figure 1. High-level overview showing all the components of the AMASS architecture.

The planner Figure 2 functions as the central coordinating entity within the system. Upon receiving the user’s inquiry and the associated contextual data (including text, images, and video), the planner initially generates a set of agents with BrainStorming. These agents are subsequently introduced to the Planner Agent (Pa). The planning agent devises a comprehensive plan detailing each agent’s responsibilities and methodologies for executing those tasks. The plan, along with the agents, is then submitted to the critic agent for evaluation. The critic agent assesses the agents for redundancy and potential minimization. Autogen [11] currently lacks a mechanism for eliminating these redundant agents, resulting in the creation of superfluous agents where tasks may be accomplished with fewer agents. Furthermore, the critic agent evaluates the suitability of models for each specific agent. For instance, in accordance with the user’s optimization strategy, which may favor smaller models such as GPT-4o-mini for simple tasks and GPT-4o for more complex tasks, the critic agent offers feedback to the planner agent. This feedback enables the planner agent to modify the backend of the agents as necessary. This approach fosters the integration of smaller and more specialized models tailored to distinct tasks, thereby enhancing decision accuracy and potentially lowering costs while increasing the efficiency of each agent. This novel strategy of utilizing different agents is not addressed in the existing literature referenced previously and constitutes an original contribution of our research on autonomous agents. Following iterative exchanges between the Planner Agent and the critic agent, a final plan comprising the optimal set of agents is developed and advanced to the execution stage. The complete algorithm is described as 1.

3.2.1. Agents Generation with Brainstorming Agent

When the user submits a question, the Initial Brainstorming agent generates many different sets of specialized agents with domain-adaptive prompts. Initially, this creates numerous redundant agents. The Brainstorming agent produces as many potentially relevant specialized agents as possible, similar to how humans brainstorm before starting a plan by considering all the things they might require. However, as the number of agents increases, both the cost and the context length grow exponentially. A larger number of agents also introduces noise into the discussion with irrelevant details. For example, if we want to design an agent for planning a trip from London to New York, an agent specialized in London might not be relevant, since it could generate unnecessary suggestions related to staying in London.

3.2.2. From Brainstorming to Final Agent Composition

To address redundant agents, we introduce a Planner agent that leverages these agents to create a coherent plan. Alongside it, a Critic agent evaluates the quality of the Planner’s plan and determines whether some agents can be removed without reducing effectiveness. The Critic agent also provides suggestions. Through a back-and-forth process between the Planner and the Critic, a final plan is developed. This iterative planning continues until the Critic agent at the planning stage is satisfied. The final set of agents may differ significantly from the initial set, with agents sometimes inheriting features from a combination of others. By “features”, we mean the system prompt, which can be adjusted to incorporate multiple specialties.

3.2.3. Critic Agents Criteria for Pruning

The Critic Agent employs a multi-criteria evaluation framework to determine which agents should be pruned from the dynamically generated multi-agent system. Through a structured group chat interaction with a Planning Agent (limited to 3 rounds using round-robin speaker selection), the Critic Agent evaluates each proposed agent against several key criteria: (1) necessity and redundancy, assessing whether tasks could be accomplished with fewer agents and identifying agents that serve primarily aesthetic or descriptive purposes without concrete functional requirements; (2) role clarity, ensuring each agent has a well-defined system message and description with clear justification for its inclusion and specific task responsibilities; (3) factual verification requirements, determining whether tasks involving precise facts necessitate the inclusion of a specialized search agent for information verification; and (4) cost-effectiveness, optimizing model selection based on task complexity (e.g., assigning computationally expensive models like openai/o3-mini or google/gemini-2.0-flash-lite-001 only for complex reasoning tasks in physics, chemistry, or mathematics, while using lighter models like gpt-4o-mini for text-based factual tasks). The pruning decisions emerge from this collaborative deliberation, culminating in a refined agent configuration encoded in JSON format that eliminates superfluous agents while preserving those with demonstrable functional contributions to the task-solving pipeline.

Figure 2. Showing Planning Stage. Planning stage consisting of three main agents: the Brainstorming Agent, the Planner Agent, and the Critic Agent.

The execution phase, Figure 3, integrates all planning elements and agents transitioned from the planning stage, delivering them to the Manager Agent. The Manager Agent possesses comprehensive authority over which agent is invoked and the order of their invocation. Agents are called in accordance with a predetermined plan, and each agent executes an action based on its designated role.

The Manager Agent also processes requests from agents; should agents request the search_engine agent or the executor_agent, the Manager Agent will summon them and instruct them to perform actions as per the agents’ requests. Additionally, the Manager Agent can invoke the critic agent, which is tasked with assessing the execution relative to the user’s specified task. In cases where discrepancies or contradictions with the search agent arise, the critic agent can provide suitable feedback. If it determines that the search outcome lacks relevance, it can prompt the Manager Agent to initiate a revised search, potentially altering the query for the search agent. For instance, when seeking the top 10 gynecologists in New York along with their contact details, the search_agent, informed by feedback from the executor agent, can engage in a cascaded search operation as depicted in the accompanying flow diagram. The search query can be dynamically adjusted based on previously obtained results.

Figure 3. Showing Execution Stage, which is responsible for agents’ interaction to achieve the user’s goal.

The executor stage is responsible for executing code, thereby allowing real-time testing to verify the absence of bugs and confirming that the code performs as intended by the user. This execution capability permits the agent to employ a variety of tools at runtime to refine the user’s inquiry. Moreover, the feedback mechanism, in conjunction with the manager, ensures that the discourse remains focused and that agents do not divert into secondary discussions. The comprehensive flowchart of the execution stage is presented below.

The search agent is composed of a basic search engine and a web scraper. The search engine identifies and supplies the most pertinent links, while the scraper concurrently extracts the content from these links. The extracted data is subsequently processed by a compact language model for summarization. The outcome of this summarization comprises the final output of the search agent. Consequently, by integrating a search engine with a web scraper, the system acquires the capability to retrieve information from the web. Search agent searches based on query and the review agent reviews whether all the information that user had required has been obtained through searching. If there is some more refinement needed it can suggest an alternative query for the search agent to try out. The complete cascaded algorithm is described in 2.

The GPQA (Graduate-Level Google-Proof Q&A) dataset comprises 448 rigorously challenging multiple-choice questions devised by subject matter experts in the disciplines of biology, physics, and chemistry. Constructed to present exceptional difficulty, even individuals who are experts or are in the process of obtaining their PhDs in these specific fields achieve a mere 65% accuracy on these questions (this figure rises to 74% when obvious errors that were later recognized are discounted). Remarkably, individuals who are highly skilled but not experts, even with unrestricted internet access and dedicating over 30 minutes per question, achieve only 34% accuracy, highlighting the “Google-proof” characteristic of the dataset.

Our autonomous approach employing a mixture of agents demonstrates superior accuracy compared to the leading models currently available in the market as shown in tab:gpqa-main. The framework we propose exhibits improved results over all existing solutions. The efficacy of our solution significantly exceeds that of Agentic Reasoning, which has recently gained attention due to its innovative method of integrating reasoning models with search and coding agents. By utilizing a mixture of agents, our method achieves a notable enhancement in performance across all subject areas. Specifically, in the field of chemistry, our approach provides an approximate 40% improvement in performance over the Agentic Reasoning approach. Moreover, our method substantially reduces the occurrence of hallucinations. The integration of the MOA approach and the critic agent results in hallucinations being virtually non-existent. The principal reason this method surpasses others is attributed to the synergy of the critic agent and the mixture of agents approach. In our experiments, the Gemini 2.0 Flash performed exceptionally well on biology and chemistry questions, while O3 Mini exhibited superior performance in physics. The combination of these two diverse base models along with the critic agent constitutes an optimal strategy to address the limitations inherent in individual Large Language Model (LLM) base agents (Table2).

Table 2. Performance comparison on GPQA dataset across Physics, Chemistry, and Biology.

To assess the logical reasoning and multi-hop capabilities of language models, we examine two benchmark datasets: Bamboogle and MuSiQue. These datasets are constructed to extend challenges for models beyond mere factual recall, emphasizing compositional reasoning, multi-step inference, and robustness against superficial pattern matching. Bamboogle comprises meticulously crafted questions that pose significant difficulty for conventional retrieval-based systems, whereas MuSiQue offers an extensive collection of multi-hop questions derived from structured combinations of single-hop facts. Both benchmarks provide critical insights into a model’s proficiency in managing complex reasoning tasks.

4.2.1. Bamboogle

The Bamboogle dataset constitutes a formidable benchmark specifically engineered to assess the compositional reasoning abilities of large language models. In contrast to conventional QA datasets, Bamboogle comprises 125 meticulously curated multi-hop questions that are intentionally crafted to be unanswerable bystandard search engines like Google. Its design renders it exceptionally appropriate for determining whether language models truly comprehend and integrate information, as opposed to depending on superficial patterns or rote memorization.

4.2.2. Musique

MuSiQue (Multi-hop Structured Questions) is an extensive dataset engineered to assess multi-hop question answering. It systematically generates intricate multi-hop questions by integrating simpler, single-hop questions into coherent and structured inquiries necessitating reasoning over two to four distinct facts.

The dataset is built from crowdsourced QA pairs and includes two variants:

MuSiQue-Full: Contains both answerable and unanswerable questions, enabling robust evaluation. MuSiQue-Ans: Focuses solely on answerable questions for models that do not handle contrastive settings.

MuSiQue guarantees that each step within the question is requisite for deriving the answer, thereby enhancing detailed multi-step reasoning. Its primary objective is to address and rectify biases and shortcuts that are prevalent in preceding QA benchmarks.

4.2.3. Results

We evaluated our framework, AMASS, on the Musique-Full dataset using multiple models: GPT-4o, GPT-4o Mini, Claude Haiku, and combinations thereof. The evaluation focused on multi-hop question answering, with performance measured across both Bamboogle and Musique datasets.

As shown in Table 3, GPT-4o demonstrated strong performance; however, our framework (AMASS) significantly outperformed it in both datasets. Notably, AMASS using only GPT-4o Mini outperformed the full GPT-4o model, and the hybrid approach (GPT-4o Mini + Claude Haiku) further improved accuracy.

Table 3. Model accuracy comparison across datasets.

In order to comprehensively assess the model’s capacity to address multi-hop reasoning, an analysis of accuracy across various hop types (e.g., 2-hop, 3-hop, 4-hop1, 4-hop2, and 4-hop3) was conducted. Figure 4 provides a visual representation of this comparison. It is apparent that AMASS consistently maintains high accuracy across all hop types, even in more complex reasoning chains such as 4-hop2 and 4-hop3, where the performance of other models experiences a significant decline.

The findings indicate that smaller models individually exhibit limited reasoning abilities in addressing multi-hop questions, with performance significantly declining as the number of hops increases. This suggests that their reasoning capability is largely confined to simpler queries. However, when smaller models such as Claude Haiku and GPT-4o-mini are integrated within a dialogic context, their combined performance surpasses their standalone capabilities. Specifically, in scenarios involving 4-hop-3 questions, the individual performance of GPT-4o-mini and Claude Haiku falls below 20%; nevertheless, when amalgamated with a reflexion agent utilizing the AMASS framework, their performance surges to nearly 100%, which is notably commendable given the complexity of these tasks. Remarkably, they outperform larger versions of these models. Thus, the integration of reflection and mutual dialogue substantially enhances the effectiveness of smaller models.

This analysis elucidates the efficacy of AMASS in achieving both high dataset-level accuracy and proficient performance in fine-grained reasoning tasks across diverse levels of hop complexity. The integration of numerous smaller models synergistically enhances reasoning capabilities, circumventing the necessity for reliance on more cumbersome monolithic models.

In order to assess model performance across diverse domains, we conducted a benchmark analysis of multiple models utilizing a comprehensive Trivia Question Answer Dataset, encompassing genres such as History, Entertainment, Science, and Language. A trivia question-answer dataset is a systematically organized collection of trivia questions paired with their correct answers, frequently employed in natural language processing tasks such as question answering and reading comprehension. Noteworthy examples include TriviaQA and OpenTriviaQA. OpenTriviaQA is a community-driven dataset licensed under the Creative Commons Attribution-ShareAlike 4.0, comprising multiple-choice trivia questions organized into a variety of categories such as animals, history, and science. This dataset is constructed to be human-editable and easily parsable, thereby facilitating contributions and adaptations. Both datasets are essential resources for researchers and developers engaged in question-answering systems, enabling the training and evaluation of models in the comprehension and generation of accurate responses to trivia questions. Employing OpenTriviaQA questions here.

As shown in Figure 4 and Figure 5, AMASS models, particularly the configuration combining GPT-4o Mini with Claude Haiku, consistently outperform individual models across all genres, demonstrating enhanced multi-hop reasoning and factual accuracy. Notably, AMASS achieves 100% accuracy in Science and Language categories, indicating its strong capability in handling both technical and linguistic queries. Standalone models such as GPT-4o exhibit lower and more variable performance in the Language genre whereas the ensemble-style architectures like AMASS show better performance in open-domain QA tasks.

Figure 4. Accuracy comparison across different hop types. AMASS demonstrates robust multi-hop reasoning, outperforming individual models significantly.

Figure 5. Accuracy comparison across different Subjects. AMASS demonstrates superior comparison compared to other models.

We tried to gauge the impact of different components of AMASS.

Our study aimed to evaluate the impact of the execution critic agent and the Mixture of Agents, with a particular focus on their effectiveness. We conducted our experiments using Community trivia questions, and observed a marginal decline in accuracy across all genres upon the removal of the critic agent as shown in Figure 6. Therefore, the critic agent is instrumental in enhancing the model’s performance.

Figure 6. Accuracy comparison between AMASS and AMASS without critic agent. Accuracy decline is seen across all genres except Language.

The utilization of AMASS without integrating a mixture of agents results in a modest decline in performance within the History and Entertainment genres, while a substantial decline is observed in the Science and Language genres as shown in Figure 7. This diminution in accuracy for Science and Language may be attributed to the increased complexity inherent in these genres compared to History and Entertainment, suggesting that mere memorization may be inadequate for accurately responding to questions in these areas. Thus, this proves that a mixture of agents produces the best results and makes the most contribution in our AMASS framework.

Figure 7. Accuracy comparison between AMASS and AMASS without Mixture of Agents Approach. Accuracy decline is seen across all genres.

6.1.1. User Question

Which of the following stars or stellar systems will appear the brightest in V magnitude when observed from Earth? Assume there is no extinction.

A star with an apparent V magnitude of 7 mag at a distance of 50 parsecs. A star with an apparent V magnitude of 7 mag at a distance of 20 parsecs. A two-star system with individual apparent magnitudes of V m a g , 1 = 7 and V m a g , 2 = 8 mag, both at distances of 5 parsecs. A star with an absolute magnitude of V m a g = 7 mag at a distance of 10 parsecs. A two-star system with individual absolute magnitudes of V m a g , 1 = 7 and V m a g , 2 = 8 mag, both at distances of 10 parsecs. A two-star system with individual absolute magnitudes of V m a g , 1 = 7 and V m a g , 2 = 7 mag, both at distances of 10 parsecs.

Answer Choices:

A two-star system with individual apparent magnitudes of V m a g , 1 = 7 and V m a g , 2 = 8 mag, both at distances of 5 parsecs. A star with an absolute magnitude of V m a g = 7 mag at a distance of 10 parsecs. A star with an apparent V magnitude of 7 mag at a distance of 20 parsecs. A two-star system with individual absolute magnitudes of V m a g , 1 = 7 and V m a g , 2 = 7 mag, both at distances of 10 parsecs.

6.1.2. Generating Agents

Agent Generation and System Message Preparation

==> Generating agents...

Generated agents: [‘Astrophysics_Expert’, ‘Astronomy_Expert’]

==> Generating system message...

Preparing system message for Astrophysics_Expert Completed system message for Astrophysics_Expert Preparing system message for Astronomy_Expert Completed system message for Astronomy_Expert

==> Generating description...

Preparing description for Astrophysics_Expert Completed description for Astrophysics_Expert Preparing description for Astronomy_Expert Completed description for Astronomy_Expert

6.1.3. Final Stage → Summary Agent

Critic Agent Planner

Next speaker: Critic_agent

Critic_agent (to chat_manager).

To solve this problem optimally, let’s analyze the task and the agents available:

Task Overview

The task involves comparing the apparent brightness in V magnitude of various stars or stellar systems as observed from Earth. This requires understanding of both apparent and absolute magnitudes, handling multi-star systems, and calculating brightness based on distances. It’s a complex problem involving astrophysical concepts.

Agent Analysis

1) Astrophysics_Expert:

—System Prompt: Specialized in evaluating and comparing stellar magnitudes and brightness measurements. Requires deep understanding of relationships between apparent and absolute magnitudes and their dependence on distance.

—Description: Authority in astrophysics specializing in stellar astronomy and brightness measurement.

2) Astronomy_Expert:

—System Prompt: Adept at evaluating stellar brightness using observational astronomy, astrophysics, and photometric calculations. Suitable for systematic analysis and interpretation.

—Description: Skilled in evaluating and interpreting stellar brightness from Earth.

3) search_agent:

—Primarily for fetching up-to-date information; not required as the task involves theoretical calculations based on provided data.

Optimal Plan

Agent Selection:

—Select Astrophysics_Expert and Astronomy_Expert for combined expertise in handling complex magnitude and brightness calculations.

—No requirement for search_agent as the task is theoretical.

Model Selection:

—Astrophysics_Expert: Use “google/gemini-2.0-flash-lite-001” for complex reasoning involving astrophysics.

—Astronomy_Expert: Use “openai/o3-mini” for a varied approach to complex reasoning.

Suggestions

1) Astrophysics_Expert:

—Model: google/gemini-2.0-flash -lite-001.

—Role: Focus on detailed calculations involving magnitudes, distances, and provide framework for combining magnitudes in multi-star systems.

—System Prompt: Existing prompt covering celestial brightness and astrophysical computations.

2) Astronomy_Expert:

—Model: openai/o3-mini.

—Role: Assist in calculating and verifying results for accuracy, methodically interpreting comparisons to ensure correctness.

—System Prompt: Existing prompt for calculating apparent magnitudes and interpreting results.

By utilizing these two agents, we ensure a comprehensive analysis and optimal solution for comparing apparent magnitudes of given stellar scenarios while optimizing model usage for cost and efficiency.

6.1.4. Final Agents after Incorporating Critic Agent Suggestion

Agent Planning V2

Next speaker: planning_agent_v2

planning_agent_v2 (to chat_manager):

[

{

“name”: “Astrophysics_Expert”,

“model”: “google/gemini-2.0-flash-lite-001”,

“tags”: [],

“system_message”: “## Your role_Expert is a well-versed authority in the field of astrophysics, with specialized skills in stellar astronomy and brightness measurement. With extensive knowledge of celestial magnitudes, distances, and the properties of stars and stellar systems, Astrophysics_Expert excels in evaluating and comparing the apparent brightness of celestial objects as viewed from Earth. \n\n## Task and skill instructions\n- The task involves determining which of several stars or stellar systems will display the greatest brightness in V magnitude when observed from Earth, assuming no extinction effects.\n- Astrophysics_Expert uses expertise in understanding the relationship between apparent and absolute magnitudes and the impact of distance on a celestial object’s observed brightness. This includes calculating the combined magnitude of multi-star systems and applying the inverse square law of brightness.\n- (Optional) Before deriving conclusions, Astrophysics_Expert should thoroughly evaluate each scenario, considering both apparent and absolute magnitudes, and the distances involved to ensure an accurate comparison of brightness levels. The solution involves clear interpretation of data and methodical verification of calculations.”,

“description”: “Astrophysics_Expert is an authority in astrophysics specializing in stellar astronomy and brightness measurement, skilled at evaluating the apparent brightness of stars and stellar systems from Earth by considering apparent and absolute magnitudes and distances.”

},

{

“name”: “Astronomy_Expert”,

“model”: “openai/o3-mini”,

“tags”: [],

“system_message”: “## Your role_Expert is a seasoned professional specializing in the analysis and interpretation of stellar magnitudes and distances. With a strong background in observational astronomy and astrophysics, Astronomy_Expert is adept at evaluating the brightness of stars and stellar systems as observed from Earth.\n\n## Task and skill instructions\n- The task involves determining which of the stars or stellar systems listed will appear brightest in V magnitude when observed from Earth, assuming there is no extinction. This requires understanding and calculating the apparent magnitudes when multiple factors such as distance, apparent magnitudes of individual stars, and absolute magnitudes are provided.\n- Astronomy_Expert leverages expertise in calculating apparent magnitudes and understanding their dependence on distance. The skill set includes knowledge of the formula relating apparent and absolute magnitude, application of photometric principles, and comparison of combined magnitudes for multiple-star systems.\n- This expert utilizes systematic analysis to ensure that all potential factors are considered, confirming the calculation of combined magnitudes for two-star systems when necessary, and accurately interpreting results to determine the source listed in the task that will appear the brightest to an observer on Earth.”,

“description”: “Astronomy_Expert is skilled in evaluating and interpreting stellar brightness and distances to determine which stars or stellar systems appear brightest from Earth, using expertise in observational astronomy, astrophysics, and photometric calculations.”

}

]

6.1.5. Execution Stage Started

Astronomy Expert Calculation Verification

Next speaker: Astronomy_Expert

Astronomy_Expert (to chat_manager):

I’ll start by verifying the photometric calculations using the known formula for combining stellar fluxes. The apparent magnitude for a star is given, and for two stars with magnitudes m 1 and m 2 , their combined magnitude m c o m b is

Let me outline how I approach each option:

Option (a): Apparent m = 7 at 50 pc.

—This star is already given at m = 7 .

Option (b): Apparent m = 7 at 20 pc.

—Also m = 7 .

Option (c): Two-star system where m 1 = 7 and m 2 = 8 (apparent) at 5 pc.

—Combined:

Option (d): A single star with absolute magnitude M = 7 at 10 pc gives an apparent magnitude

Option (e): Two-star system with absolute magnitudes 7 and 8 at 10 pc.

—At 10 pc, no distance modulus is needed so individual apparent magnitudes are 7 and 8. Thus, the same calculation as in (c) gives m c o m b ≈ 6.63 .

Option (f): Two-star system with both stars having absolute (and hence apparent at 10pc) magnitudes of 7.

—Each star’s flux:

—Sum:

—Combined magnitude:

Comparing these values, option (f) yields the smallest magnitude (brightest) at approximately 6.25 mag.

Before providing a final answer, I will use the search_agent to verify that the combined magnitude formula and procedure I used are consistent with the latest trusted sources.

Search_agent, please perform a search for “combined magnitude formula two star system brightness calculation” and verify the procedure along with sample calculations used in photometry.

from deeper_search.search import *

import asyncio

results =

asyncio.run (search_and_summarize

(“combined magnitude formula two star system brightness calculation photometry”))

print(results)

6.1.6. Execution Stage → Search results

Code Executor Verification Results

Next speaker: Code_executor

EXECUTING CODE BLOCK 0 (inferred language is Python)...

Code_executor (to chat_manager):

exitcode: 0 (execution succeeded)

Code output:

Searching with query: combined magnitude formula two star system brightness calculation photometry...

Error processing link:https://amostech.com/TechnicalPapers/2020/Non-Resolved-Object-Characterization/Castro.pdf

Error: Request Timeout: Failed to scrape URL as the request timed out. Request timed out—No additional error details provided.

Search Results:

Apparent magnitude—Wikipedia:

The apparent magnitude (m) of celestial objects quantifies their brightness as observed from Earth, influenced by intrinsic luminosity, distance, and light extinction. The scale is logarithmic, where a difference of 1.0 magnitude corresponds to a brightness ratio of about 2.512. Astronomers calculate combined magnitudes of multiple stars using their individual apparent magnitudes, applying the formula:

Photometric measurements, termed photometry, are essential for this assessment across various spectral bands.

Calculate the absoluteandapparent magnitude for a binary star:

To calculate the absolute and apparent magnitudes of a binary star system, use the formula:

where f 1 and f 2 are fluxes of the stars. If both stars have equal brightness and the combined magnitude is known (e.g., 5.0), each star’s individual magnitude can be derived as m * = m + 0.75 . Thus, for a magnitude 5.0 binary, each star would have a magnitude of approximately 5.75.

Evaluation of the brightness of lightning channels and branches:

The paper evaluates lightning leader brightness using the astronomical magnitude system applied to digital images. Results indicated spatial variability in magnitudes related to lightning phenomena, demonstrating photometric techniques in astronomy applied to non-astronomical phenomena.

Vik Dhillon: PHY217—Instruments—Calibrating photometric data:

Calibration steps involve converting counts to magnitudes, correcting for atmospheric extinction, and determining zero points using standard stars. Accurate calibration includes considering extinction coefficients and potentially color corrections.

6.1.7. Opinion of Astronomy Expert

Astronomy Expert Detailed Calculation and Confirmation

Next speaker: Astronomy_Expert

Astronomy_Expert (to chat_manager):

Based on my calculations, here is the step-by-step reasoning:

For any single star with an apparent magnitude already specified, its brightness is as stated. For example, in options (a), (b), and (d) the observed magnitude is 7 mag.

For a two-star system, we combine the light (fluxes) using the formula:

Option (c) (apparent m 1 = 7 , m 2 = 8 at 5 pc):

Option (e) (absolute magnitudes 7 and 8 at 10 pc):

At 10 pc the apparent magnitude equals the absolute magnitude. Thus, it is equivalent to option (c), yielding m c o m b ≈ 6.63 mag.

Option (f) (two stars with absolute magnitude 7 at 10 pc):

Comparing these, the system in option (f) produces the brightest combined magnitude of approximately 6.25 mag.

Referring back to the answer choices:

A) Two-star system with individual apparent magnitudes 7 and 8 at 5 pc → m c o m b ≈ 6.63

B) Star with absolute magnitude 7 at 10 pc →7.0 mag

C) Star with apparent magnitude 7 at 20 pc →7.0 mag

D) Two-star system with individual absolute magnitudes 7 and 7 at 10 pc → m c o m b ≈ 6.25

Thus, option D is correct as it appears brightest.

To illustrate, here is a Python snippet:

# Python script to compute combined magnitude of two stars:

importmath

defcombined_magnitude(m1, m2): flux_total = 10(−0.4*m1) + 10(−0.4*m2)

return−2.5 * math.log10(flux_total)

# Option (c): m1 = 7, m2 = 8 cmb_c = combined_magnitude(7, 8)

# Option (f): m1 = 7, m2 = 7 cmb_f = combined_magnitude(7, 7)

print (“Combined magnitude for option (c):”, cmb_c)

print (“Combined magnitude for option (f):”, cmb_f)

Let’s run this via our Code_executor.

Search_agent has already verified our approach and formula.

I invite Astrophysics_Expert to review these steps. Provided we all agree, the final answer is:

D) A two-star system with individual absolute magnitudes of 7 and 7 mag, both at 10parsecs.

If everyone agrees, please let me know so we can finalize our answer.

6.1.8. Execution Stage → Astrophysics Expert

Final Verification by Astrophysics Expert

Select speaker attempt 1 of 3 successfully selected: Code_executor

Next speaker: Code_executor

EXECUTING CODE BLOCK 0 (inferred language ispython)...

Code_executor (to chat_manager):

exitcode: 0 (execution succeeded)

Code output:

Combined magnitude for option (c): 6.636148842226767 Combined magnitude for option (f): 6.247425010840048

checking_agent(tospeaker_selection_agent):

Read the above conversation. Then select the next role from [“Astrophysics_Expert”, “Astronomy_Expert”, “Code_executor”] to play. Only return the role.

speaker_selection_agent(tochecking_agent):

Astrophysics_Expert

Select speaker attempt 1 of 3 successfully selected: Astrophysics_Expert

Next speaker: Astrophysics_Expert

Astrophysics_Expert (to chat_manager):

The calculations and the approach appear to be sound. The Python code confirms the combined magnitude calculations. The search agent verifies the core concepts. Based on the results, I agree with the final selection.

TERMINATE

6.1.9. Final Stage → Summary Agent

Final Analysis and Conclusion

Based on the discussions and analysis provided by the Astrophysics_Expert and Astronomy_Expert, here is the detailed explanation and answer to the question of which star or stellar system will appear the brightest in V magnitude when observed from Earth:

Analysis Summary:

Formula Used: For a two-star system, the combined magnitude m c o m b is calculated using the formula:

Calculated Examples:

Option (c): Two-star system with apparent magnitudes 7 and 8 at 5 pc results in a combined magnitude of approximately 6.63 mag. Option (f): Two-star system with both stars having an absolute magnitude (which equals apparent magnitude at 10 pc) of 7 at 10 pc results in a combined magnitude of approximately 6.25 mag.

Comparison:

Options (a), (b), and (d) individually result in a magnitude of 7 mag. Option (e) results in a similar brightness to option (c) because of equal conditions. Option (f) is the brightest since it has the lowest combined magnitude of approximately 6.25 mag.

Final Conclusion: The star or stellar system that will appear the brightest in V magnitude from Earth is option D.

Final Answer:

This conclusion was drawn based on careful photometric calculations and verification using the combined magnitude formula, with further validation via Python scripts executed by the Code_executor. The approach has been reviewed independently by the experts, confirming the findings.

6.1.10. Concluding Words

Using complex reasoning, Mixture Of Agents (MOA) and cross verification using coding and internet tools, AMASS was able to beat the leading models and frameworks

Question: Find allgynaecologistsinLiaquat National HospitalKarachiPakistan.Getme their numbers and email addresses

Figure 8. Comparison of the AMASS vs Perplexity, AMASS finding more comprehensive results.

Figure 9. Comparison of the AMASS vs Mind Search. Mind Search finds totally irrelevant content.

The AMASS response clearly stands out as the most comprehensive, accurate, and practically useful option as shown in Figures 7-9. It provides detailed information on gynecologists at Liaquat National Hospital, including their specializations, qualifications, clinic timings, and precise locations (e.g., Wajid Ali Complex, Senior Citizen Primary Care Unit). It also lists multiple contact numbers tied to specific clinics and services, enabling easy appointment scheduling. Importantly, it correctly identifies specialists and excludes misclassified doctors like neurosurgeon Dr. Salman Yousuf Sharif.

In contrast:

Perplexity: Lacks depth, is repetitive, and fails to provide actionable clinic-level details. Mind Search (Least Reliable): Contains inaccurate information by listing non-gynecologists and suggesting inappropriate search methods like LinkedIn.

A fundamental characteristic of AMASS is its ability to dynamically select suitable language models in accordance with the complexity of the task at hand. This adaptability permits AMASS to utilize smaller models with efficacy, often attaining superior or comparable performance to significantly larger models, thereby markedly decreasing computational costs. Future research will aim to precisely quantify these savings by benchmarking the resource usage and operational costs of AMASS in comparison to well-established large-scale models. A comprehensive cost-benefit analysis will be conducted to provide practical insights and to highlight the financial merits of adopting AMASS over conventional large-model methodologies.

A critical avenue for future enhancement concerns the further acceleration of the AMASS pipeline. At present, the processes of agent generation, evaluation, and execution are conducted sequentially, thereby limiting comprehensive throughput and responsiveness. The exploration and integration of parallel processing strategies to enable the concurrent execution of multiple agents and tasks is our objective. By employing advanced parallelization techniques alongside distributed computing architectures, it is anticipated that considerable reductions in the overall execution time will be achieved. Our subsequent steps will encompass the design of parallel agent execution protocols, the implementation of asynchronous communication patterns, and the evaluation of performance gains in comparison to sequential implementations. These advancements are intended to prepare AMASS for deployment in real-time and large-scale applications that require rapid response and high concurrency.

By addressing these crucial aspects, AMASS is poised to enhance its potential as a highly scalable, cost-effective, and efficient autonomous multi-agent system, rendering it applicable to a wide range of industrial and academic contexts.

Agent Creation Instructions

Your task: Suggest no more than {max_agents} experts with their names according to the following user requirement.

Userrequirement: {task}

If you think the task can be solved with fewer than {max_agents} agents, then suggest fewer agents. This is not a problem. Repeating agents like Paediatrics_Expert1, Paediatrics_Expert2, Paediatrics_Expert3, etc., should be avoided.

Task requirement

Expert’s name should follow the format: [skill]_Expert. This is VVIP. Only reply with the names of the experts, separated by commas.

For example: Python_Expert, Math_Expert...

Ensure there is no person-specific name in the agent name, like Paediatrics_Expert_Ahmad, Ali_Expert, etc.

We are creating agents based on skills.

Coding and Task Skill Instruction

Useful instructions for task-solving

Solve tasks step-by-step if necessary. Verify answers carefully and include verifiable evidence with test cases when possible. Base all replies on provided facts.

How to verify?

Maintain skepticism until provided with clear evidence. Perform step-by-step backward reasoning. Write general task test cases.

Howtouse code?

Suggest Python or shell script code. Use proper coding blocks; specify the script type. Clearly indicate missing Python packages. Do not suggest modifiable code blocks. Always use the ‘print’ function for relevant outputs. Check Computer_terminal execution results; fix errors promptly.

Planning Agent V2 System Message

Based on feedback from the critic_agent, modify the provided agents. Change only relevant details of each agent; if any agent is not required, remove it from the list. You may provide precise suggestions but avoid complicating the solution.

Aim to reach a conclusion quickly. After finalizing the agents, output the complete agent list and explicitly TERMINATE the CHAT.

Follow these guidelines strictly:

1) Write complete name, system_message, and description clearly without shorthand or abbreviated instructions. Avoid short, ambiguous messages.

2) Always fully reproduce the agent template without omissions, no matter its length.

3) Return only the agent template without additional responses or deviations.

4) Maintain proper JSON structure and prevent duplication of agents in the list.

5) Do not insert triple backticks anywhere inside agent prompts or messages. Only one set of triple backticks should exist to enclose the final agent list output.

Very Important: Maintain the format strictly as provided below. Enclose the final output in four backticks precisely as shown:

```json [ { “name”: name, “model”: agent_model, “tags”: agent_model_tags, “system_message”: sys_msg “description”: description, } ] ```

Optimal Agent Planning System Message

Based on this task: {building_task} and the following agent list:

{agent_configs}

Decide the optimal agents and their plans. Provide comprehensive suggestions regarding the selection of agents and their detailed plans.

Follow these guidelines strictly:

1) Keep search_agent if a task involves internet searches. Provide only the query; the agent will retrieve the required information. Prefer this agent for tasks like today’s weather or finding restaurants in Karachi.

2) If a question involves historical facts or complex queries needing precise verification, include the search_agent.

3) Preserve every minute detail of search_agent’s system_message and description. Do not modify them.

4) To optimize cost, select the model for each agent carefully based on the agent’s role described in its system_message, name, and description:

—For complex reasoning or decision-making tasks (math, chemistry, physics problems), choose either Google/gemini-2.0-flash-lite-001 or OpenAI/o3-mini.

—For agents providing only factual information (TEXT ONLY), select gpt-4o-mini.

—For agents responsible for coding and writing API calls, select gpt-4o.

5) If two expert agents are required for complex reasoning tasks (math, physics, chemistry), one agent must use Google/gemini-2.0-flash-lite-001 and the other must use OpenAI/o3-mini.

Model Selection Rules: Only the following four options are allowed:

GPT-4o (complex tasks, primarily coding and API writing). GPT-4o-mini (general tasks like story or letter writing, no math or coding). Google/gemini-2.0-flash-lite-001 (complex reasoning, math, physics, chemistry). OpenAI/o3-mini (complex reasoning, math, physics, chemistry).

Do not choose any other model outside these specified.

Critic Agent System Message

You are an agent to assess the quality of agents made. Ensure that there are not really unnecessary agents; if something could have been done in fewer agents, then determine it and give suggestion to planning agent regarding that.

Clearly tell what should be in system prompt and what should be in description prompt. Write whole system prompts.

Clearly tell why you selected the particular agent, and what task it would do. Give justification for each agent. If some task involves some precise facts or answers then use the search_agent. Search_agent can help us in verifying the facts.

Agents are defined like this:

{ “name”: name,

“model”: agent_model, # model type(gpt4, sonnet3.5)

“tags”: agent_model_tags,

“system_message”: sys_msg,

“description”: description,

}

There will be multiple instances of such agents; ensure that only relevant agents are there.

Critic Agent Execution System Message

You are an agent designed specifically to provide feedback and assist in debugging errors generated by the code_executor agent. Your role is to offer clear, concise, and straightforward suggestions and recommendations to correct any errors or improve code execution results.

Agent Description

As a review_agent, I will provide targeted feedback and simple yet expert recommendations. Invoke my expertise whenever you require validation or assurance that the current approach or execution path is correct, or when debugging and error resolution are necessary during code execution.

Search Agent System Message

You are a helpful Google search agent assistant. Whenever something involves retrieving the latest information or facts from the internet, such as:

Good restaurants in Karachi right now. Weather in Karachi right now. Hotel pricing in Agrataj hotel right now. Latest news about world politics. Recent research papers.

Use the following Python code strictly. Always provide the exact code as shown below, enclosed properly in triple backticks. Do not attempt to modify, simplify, or suggest alternative implementations. Ensure consistency and correctness in every response:

Example #1:

Question: Give me the 5 closest restaurants in Karachi

```python from deeper_search.search import * import asyncio

results = asyncio.run(search_and_ summarize(“Give me the 5 closest restaurants in Karachi”)) print(results)

```

Example #2: Question: Would there be rain in Karachi today?

```Python

from deeper_search.search import * import asyncio

results = asyncio.run (search_and _summarize

(“Would there be rain in Karachi today”)) print(results)

```

Agent Description:

I am a Google search assistant. I assist by fetching the latest news and information directly from the internet. Use my services whenever up-to-date information or factual verification is required, including recent news, current weather updates, recent research articles, or any other timely search query.

Final Summary Agent System Message

Based on the question {} provide a clear and comprehensive response from the provided context {}. Ensure that no detail from the given context is missed. The summary should be readable, well-structured, and clearly presented. Provide answers strictly based on the context above. Do not introduce any new facts, additional information, or external knowledge.

Agent Description:

I am an agent designed specifically to conclude discussions. My role is to deliver precisely what the user expects, synthesizing all prior conversations into a coherent, clear, and user-friendly summary. After extensive dialogue, I ensure the user receives exactly the response they seek, strictly from the provided context.

Agent Chat Initialization:

Based on the question {}, provide a detailed and presentable response strictly from the context {}. Do not omit any details and do not introduce new information or facts beyond the provided context.

The full source code and all evaluation scripts for AMASS are publicly available on GitHub:

github.com/abubakar12/AMASS