Skip to main content
Glama
avi892nash

PureScript MCP Server

by avi892nash
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

stop_purs_ide_server

Terminate the PureScript IDE server to release system resources after completing tasks like type checking or switching projects, disabling related IDE tools.

Instructions

Stop the PureScript IDE server to free up system resources. Use when you're done with type checking or want to switch projects. All pursIde* tools will stop working after this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:359-371 (handler)
    The core handler function that implements the logic for stopping the purs IDE server. It checks if the process is running, kills it if so, updates state variables, logs the action, and returns a JSON-formatted status message via MCP content.
    async function internalHandleStopPursIdeServer() {
    let message;
    if (pursIdeProcess) {
        pursIdeProcess.kill(); 
        pursIdeProcess = null; 
        pursIdeIsReady = false;
        logPursIdeOutput("purs ide server stopped by MCP.", "info");
        message = "purs ide server stopped.";
    } else {
        message = "No purs ide server was running.";
    }
    return { content: [{ type: "text", text: JSON.stringify({ status_message: message }, null, 2) }] };
}
  • index.js:677-681 (schema)
    The tool definition in TOOL_DEFINITIONS array, including the schema for input validation (empty object, no params required). This is returned in the tools/list MCP response.
        name: "stop_purs_ide_server",
    description: "Stop the PureScript IDE server to free up system resources. Use when you're done with type checking or want to switch projects. All pursIde* tools will stop working after this.",
    inputSchema: { type: "object", properties: {}, additionalProperties: false },
},
{
  • index.js:796-796 (registration)
    Registration of the tool name to its handler function in the INTERNAL_TOOL_HANDLERS map, which is used by the MCP tools/call request handler to dispatch calls.
    "stop_purs_ide_server": internalHandleStopPursIdeServer,

Tool Definition Quality

A4.6/5.0
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 of behavioral disclosure. It effectively communicates that this is a destructive action (server stops, other tools become unavailable) and implies it's a system resource management operation. However, it doesn't mention potential side effects like unsaved state loss or restart procedures.

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 perfectly concise with three tightly focused sentences: purpose statement, usage guidance, and consequence disclosure. Every sentence earns its place with no wasted words, and the information is front-loaded with the core action.

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?

For a zero-parameter tool with no annotations or output schema, the description provides excellent context about purpose, usage scenarios, and consequences. It could potentially mention restart procedures or confirmatory feedback, but covers the essential information needed for safe invocation.

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 tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and usage context.

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 specific action ('Stop') and target resource ('PureScript IDE server'), distinguishing it from siblings like 'start_purs_ide_server' and 'get_server_status'. It explicitly mentions the purpose of freeing system resources, which adds meaningful context beyond just the tool name.

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?

The description provides explicit guidance on when to use this tool ('when you're done with type checking or want to switch projects') and clearly states the consequences ('All pursIde* tools will stop working after this'), helping the agent understand the trade-offs and when alternatives might be appropriate.

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