Skip to main content
Glama

service_scan

Detect service names and versions running on open ports of a target, with adjustable scan intensity to balance speed and accuracy during authorized network audits.

Instructions

Detect service names/versions on open ports (intensity 0-9, higher is slower but more accurate).

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": {
      "target": "<target>"
    },
    "name": "service_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNo
targetYes
intensityNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: higher intensity is slower but more accurate. It omits other important traits for an active network probe — that it sends traffic to the target, requires authorization/scope, and expects already-open ports.

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?

A single front-loaded sentence with the resource first and the intensity hint in parentheses. No filler, nothing redundant.

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?

An output schema exists, so return values needn't be described, but with zero annotations and zero schema descriptions the definition should cover prerequisites and the target/ports formats. It does not, leaving meaningful gaps for a 3-parameter active-scanning tool.

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%, so the description must compensate, but it only explains intensity (range 0-9 plus the accuracy tradeoff). The required 'target' parameter and the 'ports' parameter (format, ranges, default empty meaning all ports) receive no explanation anywhere.

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: 'Detect service names/versions on open ports'. That is concrete enough to distinguish it from a plain port_scan or get_scan without opening schemas. It stops short of naming which sibling to use when, so full differentiation is absent.

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?

The phrase 'on open ports' implies a prerequisite (a port scan must run first) and the intensity note hints at a speed/accuracy tradeoff, so usage is implied rather than stated. There is no explicit when-to-use or when-not-to-use guidance versus os_detect, script_scan, or vuln_scan.

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