Skip to main content
Glama
trainual

Tiptap Collaboration MCP Server

by trainual

get_collaboration_health

Assess the operational status and performance of the Tiptap collaborative document service by retrieving its current health metrics for effective monitoring and troubleshooting.

Instructions

Get the health status of the Tiptap collaboration service

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler that performs a health check on the Tiptap collaboration service by fetching the /health endpoint with appropriate headers and authorization token, returning a structured text response with the result or error message.
    async () => {
      try {
        const headers: Record<string, string> = {
          'User-Agent': 'tiptap-collaboration-mcp',
          'Content-Type': 'application/json',
        };
        const token = getToken();
        if (token) headers.Authorization = token;
    
        const response = await fetch(`${getBaseUrl()}/health`, { headers });
        if (!response.ok) {
          return {
            content: [
              {
                type: 'text',
                text: `Health check HTTP error: ${response.status} ${response.statusText}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: `Health check response: ${await response.text()}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error connecting to Tiptap collaboration service: ${
                error instanceof Error ? error.message : 'Unknown error'
              }`,
            },
          ],
        };
      }
    }
  • The exported registration function that defines and registers the 'get_collaboration_health' tool on the MCP server, including name, description, empty input schema, and the handler.
    export default function registerGetCollaborationHealth(
      server: McpServer,
      getBaseUrl: () => string,
      getToken: () => string | undefined
    ) {
      server.tool(
        'get-collaboration-health',
        'Check Tiptap collaboration service health status',
        {},
        async () => {
          try {
            const headers: Record<string, string> = {
              'User-Agent': 'tiptap-collaboration-mcp',
              'Content-Type': 'application/json',
            };
            const token = getToken();
            if (token) headers.Authorization = token;
    
            const response = await fetch(`${getBaseUrl()}/health`, { headers });
            if (!response.ok) {
              return {
                content: [
                  {
                    type: 'text',
                    text: `Health check HTTP error: ${response.status} ${response.statusText}`,
                  },
                ],
              };
            }
    
            return {
              content: [
                {
                  type: 'text',
                  text: `Health check response: ${await response.text()}`,
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: 'text',
                  text: `Error connecting to Tiptap collaboration service: ${
                    error instanceof Error ? error.message : 'Unknown error'
                  }`,
                },
              ],
            };
          }
        }
      );
    }
  • src/server.ts:52-52 (registration)
    Invocation of the tool registration function during MCP server initialization.
    registerGetCollaborationHealth(server, getBaseUrl, getToken);
  • src/server.ts:8-8 (registration)
    Import of the registration function for the get_collaboration_health tool.
    import registerGetCollaborationHealth from './tools/get-collaboration-health.js';
Behavior2/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 retrieves health status but doesn't explain what that entails (e.g., uptime metrics, error rates, service availability), whether it requires authentication, or how frequently it can be called. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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 a single, clear sentence that directly states the tool's purpose without any extraneous information. It's front-loaded and efficiently communicates the essential function, making it easy for an agent to parse and understand immediately.

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 complexity of a health-check tool (which often involves metrics, status codes, or detailed outputs), the description is incomplete. With no annotations, no output schema, and minimal behavioral context, it fails to provide enough information for an agent to fully understand what the tool returns or how to interpret the results, leaving significant gaps in contextual understanding.

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 schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion about inputs.

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 with a specific verb ('Get') and resource ('health status of the Tiptap collaboration service'), making it immediately understandable. However, it doesn't distinguish this tool from potential siblings like 'get_server_statistics' or 'get_document_statistics', which might also provide health-related information, so it doesn't reach the highest score.

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 when this health check is appropriate (e.g., for monitoring, troubleshooting) or how it differs from sibling tools like 'get_server_statistics', leaving the agent to infer usage context without explicit direction.

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/trainual/tiptap-collaboration-mcp'

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