Skip to main content
Glama

get_server_status

Verify running IDE server processes to prevent resource conflicts. Checks Tree-sitter parser status and purs IDE server availability. Use before starting new IDE servers to ensure no duplicate processes.

Instructions

Check if IDE server processes are running to avoid resource conflicts. Shows status of Tree-sitter parser (lightweight code analysis) and purs IDE server (process for type checking). ALWAYS use this before starting new IDE servers to prevent running multiple processes simultaneously.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic, returning the MCP server status including version, Tree-sitter initialization status, and purs IDE server details (status, port, project path, recent logs).
    async function internalHandleGetServerStatus() {
        const statusResponse = {
            status: 'running', // Overall server status
            purescript_tools_mcp_version: SERVER_INFO.version,
            treeSitterInitialized,
            purs_ide_server_status: { // Renamed for clarity and to match test assertion expectation
                status: pursIdeProcess ? (pursIdeIsReady ? 'ready' : 'starting') : (pursIdeServerPort ? 'stopped' : 'not_started'),
                running: !!pursIdeProcess, // Keep this for direct boolean check if needed
                ready: pursIdeIsReady,
                port: pursIdeServerPort,
                projectPath: pursIdeProjectPath,
                recentLogs: pursIdeLogBuffer.slice(-10)
            }
        };
        return { content: [{ type: "text", text: JSON.stringify(statusResponse, null, 2) }] };
    }
  • index.js:558-562 (registration)
    Registration of the 'get_server_status' tool in the TOOL_DEFINITIONS array used by the 'tools/list' MCP method, including name, description, and input schema (no parameters required).
    {
        name: "get_server_status", 
        description: "Check if IDE server processes are running to avoid resource conflicts. Shows status of Tree-sitter parser (lightweight code analysis) and purs IDE server (process for type checking). ALWAYS use this before starting new IDE servers to prevent running multiple processes simultaneously.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
    },
  • index.js:792-792 (registration)
    Mapping of the tool name to its handler function in the INTERNAL_TOOL_HANDLERS object, used by the 'tools/call' MCP method.
    "get_server_status": internalHandleGetServerStatus,
  • Input schema definition for the tool: accepts an empty object (no parameters).
    inputSchema: { type: "object", properties: {}, additionalProperties: false },
Behavior4/5

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

With no annotations provided, the description carries the full burden and effectively discloses key behavioral traits: it's a read-only check (implied by 'Check' and 'Shows'), it helps avoid conflicts, and it monitors specific processes. However, it lacks details on output format or error handling, which could be useful for an agent.

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 front-loaded with the main purpose, followed by specific details and usage instructions in two concise sentences, with no wasted words—every sentence adds value to the agent's understanding.

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

Completeness4/5

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

Given the tool's complexity (simple status check with no parameters), no annotations, and no output schema, the description is mostly complete—it covers purpose, usage, and behavioral context. However, it doesn't specify what the status output looks like (e.g., success/failure indicators), leaving a minor gap.

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?

Since there are 0 parameters and schema coverage is 100%, the baseline is 4. The description adds context by explaining the tool's purpose and usage, which compensates for the lack of parameters, making it clear that no inputs are needed for this status check.

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

Purpose5/5

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

The description clearly states the tool's purpose with specific verbs ('Check', 'Shows') and resources ('IDE server processes', 'Tree-sitter parser', 'purs IDE server'), distinguishing it from siblings like 'start_purs_ide_server' or 'stop_purs_ide_server' by focusing on status checking rather than control operations.

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

Usage Guidelines5/5

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

It provides explicit guidance on when to use the tool ('ALWAYS use this before starting new IDE servers') and why ('to avoid resource conflicts', 'to prevent running multiple processes simultaneously'), with clear context for its application relative to other tools.

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/avi892nash/purescript-mcp-tools'

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