Skip to main content
Glama
AzDeltaQQ

MCP Advanced Reasoning Server

by AzDeltaQQ

hybrid_reasoning

Solve complex problems by combining multiple reasoning methods for step-by-step analysis. Input a query with current reasoning state to generate the next logical step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe problem or query to reason about
thoughtYesCurrent reasoning step
thoughtNumberYesCurrent step number
totalThoughtsYesTotal expected steps
nextThoughtNeededYesWhether another step is needed
numSimulationsNoNumber of MCTS simulations to run

Implementation Reference

  • The async handler function that executes the hybrid_reasoning tool. It validates inputs, simulates hybrid transformer + MCTS reasoning by generating the next thought step, formats a JSON response with the reasoning state, and handles errors.
      async ({ prompt, thought, thoughtNumber, totalThoughts, nextThoughtNeeded, numSimulations }) => {
        try {
          // Validate parameters
          if (!prompt) {
            throw new ValidationError("Prompt is required");
          }
          
          if (!thought) {
            throw new ValidationError("Current thought is required");
          }
          
          // In a real implementation, this would connect to a hybrid transformer+MCTS system
          // For now, we'll simulate the reasoning process
          
          // Simulated next thought generation based on hybrid approach
          let nextThought = "";
          
          if (nextThoughtNeeded) {
            // Logic for generating next thought would go here
            // For now, we'll return a simple placeholder
            nextThought = `Hybrid Reasoning (Step ${thoughtNumber + 1}/${totalThoughts}): ` +
                          `Combining transformer analysis with ${numSimulations} MCTS simulations on "${thought.slice(0, 50)}...", ` +
                          `the enhanced analysis suggests... ` +
                          `[This would be actual Hybrid Transformer+MCTS reasoning content]`;
          }
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  strategy: "hybrid_transformer_mcts",
                  originalPrompt: prompt,
                  currentThought: thought,
                  thoughtNumber: thoughtNumber,
                  totalThoughts: totalThoughts,
                  nextThought: nextThought,
                  complete: !nextThoughtNeeded || thoughtNumber >= totalThoughts
                }, null, 2)
              }
            ]
          };
        } catch (error) {
          if (error instanceof ValidationError) {
            throw error;
          } else {
            throw new ReasoningError(`Hybrid reasoning failed: ${error instanceof Error ? error.message : String(error)}`);
          }
        }
      }
    );
  • Zod input schema defining the parameters for the hybrid_reasoning tool, including prompt, current thought state, step counters, and MCTS simulation count.
      prompt: z.string().describe("The problem or query to reason about"),
      thought: z.string().describe("Current reasoning step"),
      thoughtNumber: z.number().int().min(1).describe("Current step number"),
      totalThoughts: z.number().int().min(1).describe("Total expected steps"),
      nextThoughtNeeded: z.boolean().describe("Whether another step is needed"),
      numSimulations: z.number().int().min(1).max(150).default(50).describe("Number of MCTS simulations to run")
    },
  • Registration of the hybrid_reasoning tool on the MCP server within the registerReasoningTools function, including name, schema, and handler.
      "hybrid_reasoning",
      {
        prompt: z.string().describe("The problem or query to reason about"),
        thought: z.string().describe("Current reasoning step"),
        thoughtNumber: z.number().int().min(1).describe("Current step number"),
        totalThoughts: z.number().int().min(1).describe("Total expected steps"),
        nextThoughtNeeded: z.boolean().describe("Whether another step is needed"),
        numSimulations: z.number().int().min(1).max(150).default(50).describe("Number of MCTS simulations to run")
      },
      async ({ prompt, thought, thoughtNumber, totalThoughts, nextThoughtNeeded, numSimulations }) => {
        try {
          // Validate parameters
          if (!prompt) {
            throw new ValidationError("Prompt is required");
          }
          
          if (!thought) {
            throw new ValidationError("Current thought is required");
          }
          
          // In a real implementation, this would connect to a hybrid transformer+MCTS system
          // For now, we'll simulate the reasoning process
          
          // Simulated next thought generation based on hybrid approach
          let nextThought = "";
          
          if (nextThoughtNeeded) {
            // Logic for generating next thought would go here
            // For now, we'll return a simple placeholder
            nextThought = `Hybrid Reasoning (Step ${thoughtNumber + 1}/${totalThoughts}): ` +
                          `Combining transformer analysis with ${numSimulations} MCTS simulations on "${thought.slice(0, 50)}...", ` +
                          `the enhanced analysis suggests... ` +
                          `[This would be actual Hybrid Transformer+MCTS reasoning content]`;
          }
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  strategy: "hybrid_transformer_mcts",
                  originalPrompt: prompt,
                  currentThought: thought,
                  thoughtNumber: thoughtNumber,
                  totalThoughts: totalThoughts,
                  nextThought: nextThought,
                  complete: !nextThoughtNeeded || thoughtNumber >= totalThoughts
                }, null, 2)
              }
            ]
          };
        } catch (error) {
          if (error instanceof ValidationError) {
            throw error;
          } else {
            throw new ReasoningError(`Hybrid reasoning failed: ${error instanceof Error ? error.message : String(error)}`);
          }
        }
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/AzDeltaQQ/Mcp-Reasoning-Server'

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