Keel

by seayniclabs

Overview Schema Source Related Servers Discussions Admin

Python

health

Retrieve the server version and status to confirm the Keel server is operational.

Instructions

Return server version and status.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "health"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/sounding/server.py:50-53 (handler)
The 'health' tool handler function. Registered with @mcp.tool(), returns server version and status.
```
@mcp.tool()
async def health() -> dict:
    """Return server version and status."""
    return {"status": "ok", "version": __version__}
```
src/sounding/server.py:50-50 (registration)
Registration of the 'health' tool via the @mcp.tool() decorator on the health function.
```
@mcp.tool()
```
src/sounding/__init__.py:1-3 (helper)
The __version__ constant ("0.2.0") imported and used by the health handler.
```
"""Sounding — network diagnostics MCP server."""

__version__ = "0.2.0"
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 15, 2026

TDQS

A3.9/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. The minimal description lacks details about side effects, idempotency, or potential impacts, though the operation is inherently read-only.

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, front-loaded sentence that conveys the tool's purpose efficiently with no unnecessary 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?

For a zero-parameter health check tool with no output schema, the description adequately covers what the tool does (return server version and status), meeting the completeness requirements given low complexity.

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?

There are zero parameters, so the input schema coverage is 100% trivially. The description adds no parameter-level detail, which is acceptable given no parameters exist.

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 returns server version and status, which is a specific and distinct action compared to sibling tools that focus on network diagnostics like DNS lookups or ping tests.

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 the tool is for basic server health checking, but does not explicitly state when to use it versus alternatives or provide any usage context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server