Skip to main content
Glama

security_scan

Scan any IP address for open ports and detected services, then get an A-F security grade with recommendations to address exposure.

Instructions

Free security scan of any IP address. Checks 12 common ports, detects services, gives A-F security grade with recommendations.

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": {
      "ip": "<ip>"
    },
    "name": "security_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIP address to scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/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 the operation's shape (12 ports, service detection, graded output with recommendations), which is genuinely useful beyond the schema. However, it never states whether the scan is passive or intrusive, how long it takes, whether it requires authorization for the target, or whether repeated calls are rate-limited. For a network-touching tool those omissions matter.

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?

Two sentences, front-loaded with purpose, then the concrete scope of the scan and the shape of the result. Nothing is redundant and every clause carries information.

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 tool with no output schema, the description usefully summarizes the return value (A-F grade plus recommendations). The remaining gap is behavioral: duration, intrusiveness, and authorization expectations for scanning arbitrary addresses are unaddressed, which would be the only thing left to add.

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% for the single 'ip' parameter, so the baseline is 3. The phrase 'any IP address' adds slight meaning (no restriction to private ranges or registered hosts) but gives no format or validation detail beyond the schema.

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?

The description states a specific verb and resource ('security scan of any IP address') and immediately bounds the scope: 12 common ports, service detection, A-F grade with recommendations. An agent knows exactly what it gets back, and no sibling tool in the catalog overlaps with scanning.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no prerequisite is stated for scanning an arbitrary IP address, such as authorization or ownership constraints. The word 'Free' hints at cost but nothing else routes the agent or sets boundaries; usage is only implied.

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