Skip to main content
Glama
claus-92

Super Productivity MCP Server

by claus-92

health_check

Confirm that the local REST API is reachable and the renderer is ready, ensuring reliable integration with Super Productivity.

Instructions

Checks whether the Super Productivity local REST API is reachable and the renderer is ready.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for the 'health_check' tool. Calls SpClient.health() and returns the result via the ok() helper.
    server.tool(
      "health_check",
      "Checks whether the Super Productivity local REST API is reachable and the renderer is ready.",
      {},
      async () => {
        const health = await SpClient.health();
        return ok(health);
      }
  • Zod schema for the health check response: validates server (string) and rendererReady (boolean).
    const HealthStatusSchema = z.object({
      server: z.string(),
      rendererReady: z.boolean(),
    }).passthrough();
  • SpClient.health() - Makes the actual HTTP request to the /health endpoint and returns a HealthStatus object.
    health(): Promise<HealthStatus> {
      return request("/health", HealthStatusSchema);
    },
  • src/index.ts:16-16 (registration)
    Registration of all task tools (including health_check) by calling registerTaskTools(server).
    registerTaskTools(server);
  • TypeScript interface for the health check response: server (string) and rendererReady (boolean).
    export interface HealthStatus {
      server: string;
      rendererReady: boolean;
    }
Behavior4/5

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

No annotations provided, but description discloses it is a safe read-only check with clear purpose. Does not detail error behavior, but adequate for a simple health check.

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?

Single sentence, no wasted words, front-loaded with key action.

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

Completeness5/5

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

For a parameterless health check with no output schema, the description is complete and sufficient.

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?

No parameters in schema, so description need not add param info. Baseline 4 for zero-parameter tool.

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 checks API reachability and renderer readiness, using a specific verb and resource. It distinguishes from sibling task-oriented tools.

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

Usage Guidelines4/5

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

The description implies usage for verifying system health before other operations, but does not explicitly state when not to use or alternatives. Clear enough given sibling context.

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/claus-92/super-productivity-mcp'

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