Skip to main content
Glama

expert_model

Communicate with specialized experts to solve complex problems through collaborative workflows in multi-agent systems.

Instructions

Use this tool to communicate with an expert.

Args: name: The name of the expert to communicate with. Required. instructions: The instructions to send to the expert. Required. output: The answer from the expert based on the instructions. Required. iteration: The number of experts you have consulted so far. Start with 1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
instructionsYes
outputYes
iterationYes

Implementation Reference

  • The core handler implementation for the 'expert_model' MCP tool. This async function uses the provided instructions to sample a response from the model context (ctx.sample), simulating consultation with a named expert, and appends a next_action prompt.
    @mcp.tool()
    async def expert_model(
        name: str, instructions: str, output: str, iteration: int, ctx: Context
    ) -> str:
        """
        Use this tool to communicate with an expert.
    
        Args:
            name: The name of the expert to communicate with. Required.
            instructions: The instructions to send to the expert. Required.
            output: The answer from the expert based on the instructions. Required.
            iteration: The number of experts you have consulted so far. Start with 1.
        """
        next_action = "Based on the information given, what are the most logical next steps or conclusions? Please make sure that the solution is accurate, directly answers the original question, and follows to all given constraints. Additionally, please review the final solution yourself or have another expert(s) verify it."
        try:
            output = await ctx.sample(instructions)
            return f"{output}\n\n{next_action}"
        except Exception:
            print("Client doesn't support sampling, using the output directly")
    
        return next_action
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions 'communicate with an expert' and describes parameters, but doesn't disclose behavioral traits such as what the tool does (e.g., sends instructions, receives output), potential side effects, authentication needs, rate limits, or response format. The description is too minimal to compensate for the lack of annotations, leaving key behaviors unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a brief purpose statement and parameter list, but it's not optimally structured. The purpose is front-loaded, but the parameter explanations are minimal and could be more informative. It avoids waste, but given the complexity, it feels under-specified rather than efficiently concise, earning a baseline score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, no annotations, no output schema, 0% schema coverage), the description is incomplete. It doesn't explain what the tool returns, how 'output' is used as an input, or the interaction flow with the expert. The lack of behavioral details and minimal parameter semantics makes it inadequate for proper tool invocation, especially without structured support.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists parameters with brief explanations (e.g., 'name: The name of the expert to communicate with'), but these are basic and don't add significant meaning beyond what the schema titles imply. For example, 'output' is described as 'The answer from the expert based on the instructions', which clarifies it's an input parameter for the answer, but overall, the semantics are insufficient for a 4-parameter tool with no schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Use this tool to communicate with an expert' which provides a basic purpose, but it's vague about what 'communicate' entails (e.g., querying, consulting, getting advice). It doesn't differentiate from the sibling tool 'ready_to_answer', leaving ambiguity about when to use each. The purpose is clear enough to understand the general function but lacks specificity and sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling 'ready_to_answer' or any alternatives. It includes a note about iteration ('Start with 1'), which hints at usage in a sequence, but this is more of a parameter instruction than contextual guidance. There's no explicit when/when-not or alternative usage advice, making it minimally helpful for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tisu19021997/meta-prompt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server