Skip to main content
Glama

host_summary

Generate a readable target report summarizing OS guesses, open ports, service versions, and default script findings so you can assess exposed services.

Instructions

Produce a readable report for a target: OS guess, open ports, versions, default script findings.

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": "host_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does not disclose whether the tool issues live network traffic to the target (and thus needs authorization), how long a run takes, whether it is repeatable, or whether results come from stored scan data. The word "default script findings" hints at NSE-style scripts but explains nothing about risk or prerequisites.

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 compact sentence with the report contents front-loaded and no filler. It is efficient, though the compression is partly why behavioral and parameter detail is missing.

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?

An output schema exists so return values need not be explained, but two things an agent still needs are absent: target format and whether the tool performs live scanning versus summarizing. For a tool that appears to run multiple detection phases in one call, that is a substantive gap.

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 coverage is 0% and the description says nothing about the single required `target` parameter. It does not state whether target is a hostname, IP, CIDR range, or URL, nor whether multiple targets or ports can be supplied. That is precisely the information the description needed to compensate for.

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?

"Produce a readable summary report" is a specific verb+resource, and the description enumerates the report contents (OS guess, open ports, versions, default script findings). It is clear what the output covers, though it never says whether it actively scans the target or aggregates existing scan data, which matters against siblings like port_scan, os_detect and script_scan.

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 when-to-use or when-not-to-use guidance is given, and no alternatives are named. An agent cannot tell whether to call this instead of quick_scan, port_scan, or os_detect, or whether it belongs at the start or end of a workflow.

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