Skip to main content
Glama

net_tools_port_scan

[$x402 pago por llamada] Escanea puertos TCP de un host (conexión directa, 3s de timeout por puerto, en paralelo).

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_tools_port_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
portsNoLista de puertos separados por coma (máx. 50). Si se omite, escanea un set de puertos comunes.
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: connect-scan semantics, 3s per-port timeout, and parallel execution are genuinely useful disclosures. However, it omits authorization/legal requirements, rate/volume limits (beyond the schema's 50-port cap), and what the scan reports (open/closed/filtered).

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?

One sentence, front-loaded with the payment tag and then the core action, with zero filler. The bracketed payment prefix is slightly cryptic but earns its place by flagging a cost constraint before the agent commits.

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?

No annotations and no output schema, so the description must cover the full contract. It never says what a successful response contains or what happens on a partial/failed scan, and it does not state the ownership/authorization prerequisite that matters most for a port scanner.

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 coverage is 67% and both optional parameters (ports with the 50-max note, x_payment with the 402 behavior) are already documented in the schema. The description adds no parameter-level meaning such as port syntax, default port set contents, or host format — baseline 3 applies.

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?

States a specific verb+resource ("Escanea puertos TCP de un host") that is unambiguous and clearly distinct from the other net_tools siblings (ping, traceroute, dns_lookup). It does not explicitly name an alternative or contrast scope, so it stops short of 5.

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?

No guidance on when to use this versus net_tools_ping or net_tools_traceroute, no prerequisites (authorization/ownership of the host), and no exclusions. The only usage-relevant hint is implicit in "conexión directa".

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