Skip to main content
Glama

thanaton_dual_probe

Probe an HTTP health endpoint and fall back to a raw TCP handshake on the guest port to detect silent false-positive deploy failures.

Instructions

Adaptive Dual-Liveness Probe: Probes HTTP endpoint and automatically falls back to raw TCP 3-way handshake on guest port, eliminating silent false-positive deploy failures.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "port": "<port>"
    },
    "name": "thanaton_dual_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYesTarget port inside guest (e.g., 3000, 8080)
health_pathNoHealth check URL path (e.g., /health, /)
target_hostNoTarget host IP or hostname (default: 127.0.0.1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the important adaptive behavior (HTTP first, then raw TCP handshake fallback on the guest port), which is genuine value. However, it says nothing about timeouts, whether the probe is non-mutating/safe, what a failure result looks like, or what the caller receives, which matters for a liveness check.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the tool's identity front-loaded and the fallback behavior stated immediately after. Mildly promotional phrasing ('eliminating silent false-positive deploy failures') but it is short and contains no filler.

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?

For a 3-parameter probe with no annotations and no output schema, the description covers the core mechanism but omits result semantics and failure/timeout behavior, which an agent needs to interpret the probe outcome. Adequate but with clear gaps for a verification tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description hints at how parameters interact (health_path drives the HTTP probe; port is the guest port used for the TCP fallback), which adds a little meaning, but it does not document defaults or formats beyond what the schema already states.

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 names a specific verb (probes) and resource (HTTP endpoint), plus the fallback mechanism (raw TCP 3-way handshake on guest port). This clearly distinguishes it from siblings like thanaton_expose_port or thanaton_list_ports, though it does not explicitly name an alternative tool.

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?

Usage is only implied: the phrase 'eliminating silent false-positive deploy failures' suggests it is used to verify a deployed service is genuinely live after a deploy. There is no explicit when-to-use/when-not guidance and no named alternative (e.g., logs or port listing) for other verification needs.

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

Deploy Server

Other Tools