Skip to main content
Glama
dmang-dev

mcp-dolphin

dolphin_ping

Verifies the Dolphin Python bridge is reachable and responding. Call at session start to confirm connectivity before using other tools.

Instructions

PURPOSE: Verify the Dolphin Python bridge is reachable and responding. USAGE: Call once at session start before other tool calls. Issues the bridge's bridge.ping method — doubles as a liveness probe and bridge-version sniff. BEHAVIOR: No side effects. mcp-dolphin connects to the bridge on demand (TCP 127.0.0.1:55355 by default). The bridge must be loaded inside Dolphin via Scripting → Add New Script → mcp_bridge.py. 10-second timeout if the bridge isn't running, Dolphin isn't running, or the port is wrong. RETURNS: Single line 'OK — bridge vBRIDGE_VERSION (DOLPHIN_LABEL)'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:66-74 (registration)
    Tool definition/registration for dolphin_ping in the TOOLS array. Declares name, description, and empty input schema.
    {
      name: "dolphin_ping",
      description:
        "PURPOSE: Verify the Dolphin Python bridge is reachable and responding. " +
        "USAGE: Call once at session start before other tool calls. Issues the bridge's `bridge.ping` method — doubles as a liveness probe and bridge-version sniff. " +
        "BEHAVIOR: No side effects. mcp-dolphin connects to the bridge on demand (TCP 127.0.0.1:55355 by default). The bridge must be loaded inside Dolphin via Scripting → Add New Script → mcp_bridge.py. 10-second timeout if the bridge isn't running, Dolphin isn't running, or the port is wrong. " +
        "RETURNS: Single line 'OK — bridge vBRIDGE_VERSION (DOLPHIN_LABEL)'.",
      inputSchema: { type: "object", properties: {} },
    },
  • Handler implementation for dolphin_ping in the CallToolRequestSchema switch. Calls bridge.ping RPC and returns formatted OK string.
    case "dolphin_ping": {
      const r = await dol.call<{ bridge_version: string; dolphin: string }>("bridge.ping");
      return ok(`OK — bridge v${r.bridge_version} (${r.dolphin})`);
    }
  • Schema definition for dolphin_ping — empty inputSchema (no params required) and the ok() helper used to format output.
    {
      name: "dolphin_ping",
      description:
        "PURPOSE: Verify the Dolphin Python bridge is reachable and responding. " +
        "USAGE: Call once at session start before other tool calls. Issues the bridge's `bridge.ping` method — doubles as a liveness probe and bridge-version sniff. " +
        "BEHAVIOR: No side effects. mcp-dolphin connects to the bridge on demand (TCP 127.0.0.1:55355 by default). The bridge must be loaded inside Dolphin via Scripting → Add New Script → mcp_bridge.py. 10-second timeout if the bridge isn't running, Dolphin isn't running, or the port is wrong. " +
        "RETURNS: Single line 'OK — bridge vBRIDGE_VERSION (DOLPHIN_LABEL)'.",
      inputSchema: { type: "object", properties: {} },
    },
  • Python bridge handler for the 'bridge.ping' RPC method. Returns bridge version and Dolphin label.
    def _ping(_p):     return {"bridge_version": BRIDGE_VERSION, "dolphin": "Felk Python fork"}
    def _status(_p):   return {"state": "unknown (use dolphin_pause/dolphin_resume to control — but see bridge known-limitation about paused-deadlock)"}
  • Registration of bridge.ping in the Python bridge HANDLERS dispatch table.
    HANDLERS = {
        "bridge.ping":                    _ping,
        "bridge.status":                  _status,
Behavior5/5

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

With no annotations, description covers all behavioral traits: no side effects, timeout, connection details, prerequisites (bridge must be loaded). Discloses internal mechanism and error conditions.

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?

Well-structured with labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Concise yet comprehensive, no wasted words.

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?

Completely covers all relevant aspects for a zero-parameter tool: purpose, usage, behavior, and return value. No output schema needed; description handles it.

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. Baseline 4 for 0 params. Description adds value by explaining return format, but not required.

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?

Explicitly states purpose: verify bridge reachable and responding. Clearly distinct from sibling tools (e.g., dolphin_read*, dolphin_press_*).

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?

States 'Call once at session start before other tool calls,' providing clear usage context. Does not explicitly mention when not to use or alternatives, but is sufficient.

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/dmang-dev/mcp-dolphin'

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