Skip to main content
Glama
plutzilla

Omnisend MCP Server

ping

Check if the Omnisend MCP Server is running correctly to verify connectivity before performing marketing platform operations.

Instructions

Simple tool to check if the MCP server is running correctly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the "ping" tool. It returns a structured response confirming the MCP server is operational and includes the server version.
    async () => {
      return {
        content: [{ type: "text", text: `Omnisend MCP server is working correctly. Server version: ${SERVER_VERSION}` }]
      };
    }
  • Registers the "ping" tool on the McpServer instance, including name, description, empty input schema, and the handler function.
    server.tool(
      "ping",
      "Simple tool to check if the MCP server is running correctly.",
      {},
      async () => {
        return {
          content: [{ type: "text", text: `Omnisend MCP server is working correctly. Server version: ${SERVER_VERSION}` }]
        };
      }
    );
  • src/index.ts:30-30 (registration)
    Invokes registerPingTool to add the "ping" tool to the main MCP server.
    registerPingTool(server);
  • Re-exports the registerPingTool function from ping.ts for use in other modules.
    export { registerPingTool } from './shared/ping.js';
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. It discloses that this is a 'simple tool' for checking server status, which implies a read-only, non-destructive operation. However, it lacks details on response format, error handling, or rate limits, making it adequate but incomplete for behavioral context.

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, efficient sentence that front-loads the purpose ('Simple tool to check if the MCP server is running correctly') with zero wasted words. It's appropriately sized for a simple tool and every part earns its place.

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

Completeness4/5

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

Given the tool's low complexity (0 parameters, no output schema, simple purpose), the description is mostly complete. It explains what the tool does and its intent. However, without annotations or an output schema, it could benefit from mentioning expected responses or error cases for full completeness.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it appropriately doesn't mention any, earning a baseline score for tools with no parameters.

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 checking if the MCP server is running correctly, which is a specific verb ('check') with a clear resource ('MCP server'). However, it doesn't distinguish from sibling tools like 'sendEvent' which might also indicate server responsiveness, so it misses full 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 Guidelines3/5

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

The description implies usage for server health checks ('check if the MCP server is running correctly'), providing some context. But it doesn't explicitly state when to use this versus alternatives like 'sendEvent' for testing connectivity, nor does it mention exclusions or prerequisites, leaving room for ambiguity.

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/plutzilla/omnisend-mcp'

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