Skip to main content
Glama
oaslananka

MCP Health Monitor

Unregister Server

unregister_server
Destructive

Stop monitoring a server by providing its name. Removes the server from health checks and alerts.

Instructions

Remove a server from monitoring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • Core handler: deletes the server from the SQLite database by name and returns a confirmation.
    export function unregisterServer(name: string): { unregistered: true; name: string } {
      getDb().prepare('DELETE FROM servers WHERE name = ?').run(name);
      return { unregistered: true, name };
    }
  • src/app.ts:728-741 (registration)
    Registration of the 'unregister_server' MCP tool with metadata and a handler lambda that delegates to unregisterServer().
    server.registerTool(
      'unregister_server',
      {
        title: 'Unregister Server',
        description: 'Remove a server from monitoring.',
        inputSchema: UnregisterSchema,
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          openWorldHint: false
        }
      },
      async (input: UnregisterInput) => formatResponse(unregisterServer(input.name))
    );
  • Input schema for unregister_server: requires a 'name' string field.
    export const UnregisterSchema = z.object({
      name: z.string()
    });
  • TypeScript type inferred from UnregisterSchema for the unregister_server input.
    export type UnregisterInput = z.infer<typeof UnregisterSchema>;
  • Import statement pulling the unregisterServer function into app.ts where the tool is registered.
    import {
      decodePatToken,
      getAzurePipeline,
      getDashboardReport,
      getLatestHealthCheck,
      getServer,
      getUptimeHistory,
      listAzurePipelineGroups,
      listAzurePipelines,
      listServers,
      recordHealthCheck,
      recordPipelineRun,
      registerAzurePipelines,
      registerServer,
      unregisterServer
    } from './registry.js';
Behavior2/5

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

Annotations already set destructiveHint=true, so the description adds minimal extra behavioral context. It does not detail consequences (e.g., irreversible? affects ongoing checks?) beyond the basic action.

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, short sentence with no redundancy. It is front-loaded and efficient, though it could arguably benefit from a bit more detail.

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 simplicity (one parameter, destructive hint, no output schema), the description barely covers the essentials. It lacks parameter explanation and post-condition information, leaving an agent with insufficient context for safe use.

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?

Schema description coverage is 0%, but the description provides no explanation of the 'name' parameter (e.g., what identifier/format). The agent has no additional context beyond the schema's type definition.

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 'Remove a server from monitoring' clearly identifies the action (remove), resource (server), and context (from monitoring). This distinguishes it from siblings like 'register_server' (add) and 'list_servers' (list).

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

Usage Guidelines3/5

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

The description implies the tool is for unregistering a server that has been previously registered, but it does not explicitly state when to use it over alternatives or provide exclusions. No guidance on prerequisites or conditions.

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/oaslananka/mcp-health-monitor'

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