Skip to main content
Glama

Open ports of a monitor's host

get_ports
Read-only

For a monitor with port_scan on (Business plans): which of its host's addresses are verified and how to verify the rest (a file each address serves, or reverse DNS under the host with a TXT record), the ports the last weekly scan found open, flagged where the service usually should not be public, and the recent scans. 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": "get_ports"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

placeholder

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 dense sentence, front-loaded with the eligibility condition before the payload, so the agent gets the gating fact first. The nested parenthetical about files and reverse DNS is awkward but brief; almost nothing is wasted.

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?

For a one-parameter read tool with readOnlyHint and no output schema, the description covers eligibility, cost ('Free'), data freshness (weekly scan cadence) and the shape of the returned data — the main things the structured fields cannot convey. It stops short of failure behavior when port_scan is off, which is the remaining gap.

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 100% and the single id parameter is documented as a monitor UUID from list_monitors, so the baseline applies. The description adds one real constraint — the referenced monitor must have port_scan active on a Business plan — which narrows what a valid id is, but it doesn't say what happens if the monitor lacks port_scan.

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 enumerates the concrete payload precisely: verified host addresses and how to verify the rest, ports found open by the last weekly scan, risk flags, and recent scans. That is effectively a purpose statement, though it is delivered as a noun-phrase list with no verb, and it never names a sibling (scan_ports, verify_host) to distinguish scope.

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?

It states a clear precondition — the monitor must have port_scan enabled, Business plans — which tells the agent when the call is valid. It offers no alternative routing, however: 'how to verify the rest' describes data rather than pointing at verify_host, and nothing says where to go to trigger a scan.

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