Skip to main content
Glama

check_port

Read-onlyIdempotent

Check whether a single TCP port on a host accepts connections to diagnose network reachability; opens and closes one connection without sending data.

Instructions

Check whether ONE TCP port on ONE host accepts connections (e.g. 443 for a website). Opens one normal connection and closes it; sends no data. Not a port scanner: limited to a few different ports per host every 10 minutes.

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>",
      "port": "<port>"
    },
    "name": "check_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
portYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds real behavioural context on top: it opens one normal TCP connection, closes it, and sends no data, which tells the agent this cannot probe application protocols. It also discloses a rate limit (a few ports per host per 10 minutes), a constraint annotations cannot express and one that materially affects retry/batching strategy.

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?

Three short sentences, front-loaded with the primary verb and scope, followed by mechanism then limitation. Every sentence adds information an agent needs; nothing is repeated from annotations or the schema.

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

Completeness4/5

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

With only two required params and an output schema present, the description covers the essentials: scope, mechanism, absence of payload data, and rate limiting. The remaining gap is the host parameter's accepted format, which neither the schema nor the description specifies.

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 0%, so the description must carry meaning for 'host' and 'port'; it clarifies port semantics with the 443/website example but says nothing about whether 'host' expects a hostname, IP literal, or URL. Partial compensation only, so this sits at the adequate baseline.

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?

States a specific verb and resource ('Check whether ONE TCP port on ONE host accepts connections') with the capitalised 'ONE' fixing the cardinality, and an inline example ('443 for a website') making the operation concrete. It also preempts the most likely misreading by declaring 'Not a port scanner', so an agent can distinguish this from a bulk-scanning capability without opening the schema.

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?

Gives a clear when-not condition ('Not a port scanner') plus the operational constraint of a few different ports per host every 10 minutes, which directly shapes how an agent should batch calls. It does not point to a sibling for adjacent needs (e.g. ping/traceroute for reachability), but the guidance on the tool's own appropriate use is unambiguous.

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