Skip to main content
Glama
dacebt

Prompt Cleaner MCP Server

by dacebt

health-ping

Check server status and confirm operational readiness for prompt cleaning and sanitization tools.

Instructions

Liveness probe; returns { ok: true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'health-ping' tool. It creates an output object { ok: true }, logs the execution time, and returns it formatted as JSON content.
    case "health-ping": {
      const out = { ok: true } as const;
      logger.info("health.ping", { elapsed_ms: Date.now() - start });
      return jsonContent(out);
    }
  • src/tools.ts:75-79 (registration)
    Tool registration in listTools(): defines name, description, and input schema (empty object) for 'health-ping'.
    {
      name: "health-ping",
      description: "Liveness probe; returns { ok: true }",
      inputSchema: { type: "object", properties: {} },
    },
  • Input schema definition for 'health-ping': accepts an empty object.
    inputSchema: { type: "object", properties: {} },
  • src/server.ts:24-27 (registration)
    MCP server registration for listing tools, which includes 'health-ping' via listTools().
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      logger.info("tools.list", {});
      return { tools: listTools() };
    });
  • src/server.ts:29-39 (registration)
    MCP server registration for calling tools, which dispatches to the 'health-ping' handler via callTool.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const name = request.params.name;
      const args = request.params.arguments ?? {};
      const requestId = (args as any)?.requestId || randomUUID();
      const withRid = { ...(args as any), requestId };
      logger.info("tools.call.start", { name, request_id: requestId });
      const res: any = await callTool(name, withRid);
      logger.info("tools.call.done", { name, request_id: requestId });
      // Return MCP-spec content unchanged (including json type when present)
      return res;
    });
Behavior3/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 states the tool returns '{ ok: true }', which implies a read-only, non-destructive operation, but doesn't cover other traits like error handling, latency, or side effects. This is adequate as a minimal disclosure but lacks depth.

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 extremely concise and front-loaded, consisting of just two phrases that directly state the tool's function and output. Every word earns its place with no waste, making it highly efficient.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is complete enough for a basic liveness probe. However, it could benefit from more context, such as when to use it or what 'ok: true' signifies, but it meets the minimum viable standard for this low-complexity tool.

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 0 parameters, and the schema description coverage is 100%, so no parameter information is needed. The description doesn't add parameter details beyond the schema, but with no parameters, this is acceptable, aligning with the baseline of 4 for zero-parameter tools.

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 tool's purpose as a 'liveness probe' that returns a specific response, which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'cleaner' or 'normalize-prompt', which appear to serve different functions, so it doesn't fully meet the highest standard for sibling differentiation.

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. It doesn't mention any context, prerequisites, or exclusions, leaving the agent without usage instructions. This is a basic gap in guidance.

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/dacebt/prompt-cleaner-mcp'

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