Skip to main content
Glama

restart_server

Restart a server by providing its ID to apply updates or resolve issues without manual intervention.

Instructions

Restart a server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesThe ID of the server to restart

Implementation Reference

  • The MCP tool handler for 'restart_server'. It accepts a 'server_id' parameter, calls client.restartServer(server_id), and returns a success message.
    server.tool(
      "restart_server",
      "Restart a server",
      {
        server_id: z.coerce.number().describe("The ID of the server to restart"),
      },
      async ({ server_id }) => {
        await client.restartServer(server_id);
        return {
          content: [
            {
              type: "text" as const,
              text: `Server ${server_id} restart initiated successfully`,
            },
          ],
        };
      }
    );
  • Zod schema definition for the 'restart_server' tool: requires 'server_id' (coerced number).
    {
      server_id: z.coerce.number().describe("The ID of the server to restart"),
    },
  • The tool is registered via server.tool('restart_server', ...) inside registerServerTools, which is called from registerAllTools in src/tools/index.ts (line 8), which is called from src/index.ts (line 127).
    server.tool(
      "restart_server",
      "Restart a server",
      {
        server_id: z.coerce.number().describe("The ID of the server to restart"),
      },
      async ({ server_id }) => {
        await client.restartServer(server_id);
        return {
          content: [
            {
              type: "text" as const,
              text: `Server ${server_id} restart initiated successfully`,
            },
          ],
        };
      }
    );
  • The client.restartServer method that makes the actual HTTP POST request to the Ploi API endpoint /servers/{id}/restart.
    async restartServer(id: number): Promise<void> {
      await this.request<void>("POST", `/servers/${id}/restart`);
    }
Behavior2/5

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

The description does not disclose any behavioral traits beyond the restart action. No annotations are provided, and the description omits critical context such as whether the restart is graceful, whether it disrupts ongoing operations, or if any logs are generated. This is insufficient for a potentially destructive operation.

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

Conciseness4/5

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

The description is a single concise sentence with no wasted words. It is appropriately sized for a simple action, though it could benefit from one additional sentence for context.

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

Completeness3/5

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

For a simple restart action, the description is minimally adequate. However, it lacks important context about side effects, such as downtime or connection drops, which would be valuable for an AI agent to know before invoking this tool.

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

Parameters3/5

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

The only parameter 'server_id' is fully described in the schema with 'The ID of the server to restart'. The description adds no additional meaning beyond the schema, and with 100% schema coverage, the baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the verb 'Restart' and the resource 'a server', making the purpose unambiguous. However, it lacks specificity about the server type and does not distinguish this tool from sibling tools like 'suspend_site' or 'deploy_project', although those are distinct enough.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, conditions under which restart is appropriate, or situations where another tool like 'get_server' or 'deploy_site' should be used instead.

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/sudanese/ploi-mcp'

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