Skip to main content
Glama

AutoPay

security_scan_full

Full passive security review (passive only): everything in quick + cookie flags, mixed content, server/version disclosure, RDAP domain age/expiry, up to 5 same-site subpages, prioritized step-by-step remediation plan. $0.99; 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_full"
  }
}

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

B3.4/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 does disclose key traits: passive-only behavior, synchronous execution, $0.99 price, charged only on success, and two payment paths (x402 USDC on Base via X-PAYMENT or prepaid API key). It also caps subpage crawling at 5. Undisclosed are execution duration/timeout, rate limits, and what a failed or partial scan returns, which matter for a paid synchronous call.

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?

Dense but front-loaded: purpose first, then the enumerated feature scope, then pricing, payment, and execution mode. Every clause carries operative information (cost, charge condition, subpage cap), though the parenthetical '(passive only)' slightly duplicates the opening phrase.

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?

For a paid, unannotated tool with no output schema, the description covers scope, price, payment, and crawling limits but omits expected latency, failure behavior, and any hint of report structure beyond the remediation plan. Adequate to select and invoke the tool, but the agent cannot anticipate timing or error handling.

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 description coverage is 100%, so the baseline is 3; the description adds nothing about parameters. The more notable gap is that the schema marks both url and domain as optional with no documented one-of relationship, and the description does not clarify that exactly one of them must be supplied, leaving an ambiguity the agent must resolve itself.

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 and resource ('Full passive security review') and enumerates scope precisely: cookie flags, mixed content, server/version disclosure, RDAP domain age/expiry, up to 5 subpages, remediation plan. It differentiates itself as a superset by saying it covers 'everything in quick', but never names the sibling tool, forcing the agent to guess which tool 'quick' refers to.

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 by the superset framing plus 'passive only', which suggests this is the comprehensive option versus narrower siblings like security_scan_headers or security_scan_tls. There is no explicit when-to-use statement, no cost-based steering against cheaper scans, and no exclusions such as 'do not use for active exploitation testing' beyond the passive qualifier.

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