Skip to main content
Glama

AutoPay

security_scan_exposure

Exposed files check (passive only): single GETs for /.git/HEAD, /.env, /server-status, directory listing, security.txt; score + grade. $0.005; 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_exposure"
  }
}

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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the passive read-only nature, synchronous execution, a concrete price ($0.005), success-only billing, and the two accepted payment mechanisms (X-PAYMENT x402 USDC on Base or prepaid API key). It stops short of covering rate limits, quota exhaustion, or failure/error behavior, which leaves a gap for an unannotated paid endpoint.

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?

The core capability is front-loaded in the first clause and the enumerated checks follow immediately, with payment logistics placed last where they belong. The semicolon-chained phrasing is dense but every clause carries invocation-relevant information, so there is little waste.

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 simple two-parameter, no-output-schema tool, the definition covers what is checked, cost, payment auth, and execution mode. The one omission is that 'score + grade' is only named, not characterized, and there is no output schema to fall back on for return-value shape.

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%, with both url and domain already documented with examples, so the baseline applies. The description adds no guidance on how the two alternatives interact (e.g., precedence if both are supplied) or which to prefer, so it does not meaningfully exceed 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?

States a specific verb and resource ('Exposed files check') and enumerates exactly what is probed (/.git/HEAD, /.env, /server-status, directory listing, security.txt), so an agent can distinguish it from security_scan_full, security_scan_headers, or security_scan_tls without opening a schema.

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?

'Passive only' and 'single GETs' implicitly tell the agent this is a lightweight, non-intrusive check rather than a deep scan, which is useful context. However, it never explicitly says when to prefer this over security_scan_full or the other siblings, nor does it state prerequisites such as requiring a reachable public host.

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