Skip to main content
Glama
evtapps

Ditto MCP Server

by evtapps

Ping

ping

Check the operational status and connectivity of the Ditto MCP server to ensure it's ready for secure database queries.

Instructions

Health check for the Ditto MCP server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'ping' tool, which returns a simple 'pong' response.
    async () => ({ content: [{ type: 'text', text: 'pong' }] }),
  • The input schema for the 'ping' tool, which is empty (no parameters expected).
    inputSchema: {},
  • src/mcpServer.ts:26-34 (registration)
    Registration of the 'ping' tool using McpServer.registerTool, including schema and handler.
    server.registerTool(
      'ping',
      {
        title: 'Ping',
        description: 'Health check for the Ditto MCP server',
        inputSchema: {},
      },
      async () => ({ content: [{ type: 'text', text: 'pong' }] }),
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this is a 'Health check' which implies a read-only, non-destructive operation, but it doesn't disclose behavioral traits like what 'health' entails (e.g., response time, status codes), whether it requires authentication, or any rate limits. The description is too vague for a tool with no annotation coverage.

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 directly states the tool's purpose without any fluff. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 annotations, no output schema), the description is minimally adequate. It explains what the tool does but lacks details on behavioral aspects like return values or error conditions. For a health check tool, more context on expected outcomes would improve 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 tool has 0 parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools by not introducing unnecessary complexity.

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 'Health check for the Ditto MCP server' with a specific verb ('check') and resource ('Ditto MCP server'). It distinguishes from the sibling tool 'execute_dql' by focusing on server health rather than data querying. However, it doesn't explicitly contrast with the sibling, so it's not a perfect 5.

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 typical use cases (e.g., verifying server availability before operations) or exclusions. The context is implied as a health check, but explicit usage instructions are missing.

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/evtapps/ditto-mcp'

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