Skip to main content
Glama

Verify a monitor's host for port scans

verify_host
Idempotent

Looks for the proof of each of the host's addresses from get_ports: the file served at the address, or its reverse DNS (PTR) under the host resolving back to it with the TXT record in place. The TXT record alone proves no address. The proof must stay in place, since every scan checks it again; only covered addresses are scanned. Free.

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": {
      "id": "<id>"
    },
    "name": "verify_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

This is the strongest part: beyond the annotations it discloses that verification performs external lookups (fetching a file at the address, reverse DNS), that the TXT record alone is insufficient, that proof must remain in place because every scan re-checks it, that only proven addresses get scanned, and that the call costs nothing. Those are real behavioral traits the agent could not derive from openWorldHint/idempotentHint alone. It does not say what happens on partial failure or what the response contains, which keeps it off a 5.

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?

Four short sentences, front-loaded with the core mechanism, then the caveat about TXT-only, then durability, then cost. Nothing is padding. Slight deduction for the slightly tangled phrasing of the PTR clause ('its reverse DNS (PTR) under the host resolving back to it with the TXT record in place'), which takes a re-read.

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 network-touching, idempotent, non-destructive operation with no output schema, the agent still lacks the return shape — whether it reports per-address pass/fail, and what a failure looks like — plus any error or retry semantics. Annotations carry the safety profile and the description carries the mechanism, but the outcome contract is missing. Adequate rather than complete.

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?

There is a single required parameter with 100% schema description coverage, so the schema already tells the agent it is a monitor UUID sourced from list_monitors. The description does not mention the id at all and adds no meaning beyond the schema. Per the stated baseline for full schema coverage, a 3 is correct.

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 states a concrete operation: it checks each of the host's addresses (obtained from get_ports) for proof of control, either a served file or a PTR-plus-TXT combination. This is far more specific than a restatement of the name 'verify_host', and it references the sibling that supplies the inputs. It stops short of naming what verification unlocks (port scanning) in a single crisp sentence, but the mechanics are unambiguous.

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 implied rather than stated: the 'addresses from get_ports' phrase tells the agent to call get_ports first, and 'only covered addresses are scanned' signals that uncovered addresses are skipped. However, there is no explicit when-to-use/when-not framing, no statement of prerequisites (DNS records must already be published), and no naming of alternatives if verification fails. The agent can infer the workflow but must do work to do so.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources