Skip to main content
Glama

get_status

Check the current status of the MCTS MCP Server, enabling real-time updates on Monte Carlo Tree Search operations for deep analysis of topics or text inputs.

Instructions

Get the current MCTS status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_status' MCP tool. It returns a dictionary containing the current MCTS server state, including initialization status, current question, chat ID, provider/model config, iterations completed, best score, and API key status.
    def get_status() -> dict[str, Any]:
        """
        Get the current MCTS status and configuration.
    
        Returns comprehensive information about the current state of the MCTS system
        including initialization status, current question, provider settings, and results.
    
        Returns:
            Dict containing all current status information and configuration
        """
        return {
            "initialized": server_state["initialized"],
            "current_question": server_state["current_question"],
            "chat_id": server_state["chat_id"],
            "provider": server_state["provider"],
            "model": server_state["model"],
            "iterations_completed": server_state["iterations_completed"],
            "best_score": server_state["best_score"],
            "has_analysis": bool(server_state["best_analysis"]),
            "available_providers": ["gemini"],
            "api_key_configured": bool(os.getenv("GEMINI_API_KEY") or os.getenv("GOOGLE_API_KEY"))
        }
  • The input schema definition for the 'get_status' tool, specifying an empty object (no parameters required). Defined within the tool registration.
    inputSchema={"type": "object", "properties": {}}
  • Registration of the 'get_status' tool in the @server.list_tools() handler, providing name, description, and input schema.
    types.Tool(
        name="get_status",
        description="Get the current MCTS status",
        inputSchema={"type": "object", "properties": {}}
    ),
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 of behavioral disclosure. 'Get the current MCTS status' implies a read-only operation, but it doesn't specify whether this requires authentication, has rate limits, returns real-time or cached data, or what format the status information takes. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness5/5

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

The description is a single, clear sentence: 'Get the current MCTS status'. It's front-loaded with the core action and resource, with no redundant words or unnecessary elaboration. This is an excellent example of conciseness for a simple tool.

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 (a status-checking tool with no output schema and no annotations), the description is incomplete. It doesn't explain what 'MCTS status' includes (e.g., operational state, error messages, performance metrics) or how the result should be interpreted. Without annotations or output schema, the description should provide more context about the return value and usage scenarios.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are none to explain. This meets the baseline of 4 for zero-parameter tools, as there's no need to compensate for missing schema information.

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 'Get the current MCTS status' clearly states the action (Get) and resource (MCTS status), making the purpose understandable. However, it doesn't differentiate this tool from its siblings like 'get_synthesis' or 'initialize_mcts', leaving ambiguity about what specifically distinguishes 'status' from other retrieval operations. The description avoids tautology but lacks specificity about what 'MCTS status' entails.

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 alternatives. With siblings like 'get_synthesis', 'list_available_models', and 'run_mcts_search', there's no indication of whether this tool is for checking system health, monitoring progress, or retrieving configuration states. The absence of usage context leaves the agent to guess based on tool names alone.

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

Related 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/angrysky56/mcts-mcp-server'

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