Skip to main content
Glama

AutoPay

security_scan

Quick passive security scan (passive only): TLS/cert, HTTPS redirect, HSTS + security headers, SPF/DMARC/DKIM/CAA/DNSSEC, exposed .git/.env/server-status/directory listing, security.txt; score + grade. $0.01; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "security_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSite URL, e.g. https://example.com
domainNoAlternative to url: bare domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses synchronous execution, cost ($0.01), that billing occurs only on success, and the two auth paths (X-PAYMENT x402 USDC on Base or a prepaid API key). It does not cover rate limits, timeout behavior, or what a failure/partial scan returns, which keeps it below a 5.

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 dense sentence group, front-loaded with what the scan covers and followed by pricing/payment facts. Every clause carries information; the semicolon-delimited list is compact rather than padded.

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 synchronous paid scan with no output schema, the description supplies the essentials an agent needs: scope of checks, the fact it is passive, cost and billing semantics, and payment mechanism. The only shortfall is a thin account of the result payload beyond 'score + grade' and no guidance on choosing url vs domain.

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%, so the schema already documents url and domain including their alternation. The description adds no parameter-level meaning (no format rules, no statement that one of the two must be supplied despite zero required parameters), so this sits at the documented baseline.

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 gives a specific verb+resource ('passive security scan') and enumerates the concrete checks performed (TLS/cert, HSTS, SPF/DMARC/DKIM, exposed .git/.env, security.txt) plus the return shape (score + grade). The '(passive only)' qualifier plus 'Quick' implicitly separates it from the active/full or per-category siblings, but it never names a sibling to route against.

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?

Usage is only implied: 'Quick passive' signals a fast first-pass check, and the listed checks suggest it overlaps with security_scan_headers/tls/dns/exposure without saying which to prefer. There is no explicit when-to-use, when-not-to-use, or named alternative such as security_scan_full for deeper or active testing.

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