Skip to main content
Glama

net

Read-only

Check DNS records, test TCP port reachability and timing, and inspect TLS certificates, expiry, and chain for a host.

Instructions

Network: dns records, reach (TCP ports, timing), tls (cert, expiry, chain).

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": {
      "host": "<host>"
    },
    "name": "net"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNo
hostYes
portNo
portsNo
typesNo
attemptsNo
timeout_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, so safety is covered, but the description adds almost nothing beyond that: no mention of default timeouts, retry semantics (the 'attempts' param suggests retries), rate limits, or that this makes live outbound network connections. For an active-probing tool, that missing context matters.

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 front-loaded line with zero filler, and the three modes are grouped logically with their outputs. It is arguably over-compressed, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 undocumented parameters, no output schema, and three distinct operating modes, the definition is far too thin for the tool's complexity. An agent would have to guess which parameters apply to which 'op' value and what results to expect.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate and does not. 'ports', 'types', 'attempts', and 'timeout_s' are never named or explained; the words 'ports', 'timing', and 'chain' only loosely gesture at them, leaving defaults and formats unknown.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names three concrete capabilities (DNS records, TCP reachability with timing, TLS certificate/expiry/chain), which is more than a restatement of the name 'net'. However, it is written as a terse fragment without a verb, and it does not distinguish this tool from the sibling 'http' or explain the relationship between the three operations and the 'op' parameter.

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?

There is no guidance on when to use this tool versus alternatives such as 'http', nor on when to pick each of the dns/reach/tls operations. No prerequisites or exclusions are stated; the parenthetical hints at what each mode returns but not when each is appropriate.

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