Skip to main content
Glama

database_audit

Scans a target for exposed MySQL, MSSQL, MongoDB, and Redis services without brute forcing credentials, helping identify unsecured database instances.

Instructions

Check for exposed MySQL, MSSQL, MongoDB, and Redis instances on a target (no brute force).

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

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses only that no brute force is performed, leaving the agent without confirmation that the scan is non-destructive, read-only, or otherwise safe to run.

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?

The definition is a single front-loaded sentence with no filler. It names the check, the database types, the target scope, and one behavioral constraint efficiently.

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?

The output schema exists, so return values need not be described, and the database technologies are enumerated. Still, for a network audit tool with no annotations, the missing target format and safety profile leave meaningful gaps.

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 description coverage for the single 'target' parameter is 0%, so the schema provides no format or scope guidance. The description says 'on a target' but does not clarify whether that means an IP address, hostname, CIDR range, or something else.

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 uses a specific verb, 'Check for exposed,' and names the exact database technologies (MySQL, MSSQL, MongoDB, Redis) plus the target scope. This clearly distinguishes it from DNS, HTTP, RDP, SSH, and other audit siblings.

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?

The purpose implies when to use it for database exposure checks, and the parenthetical '(no brute force)' sets a boundary. However, it does not explicitly say when to choose this over port_scan or service_scan, nor does it state prerequisites or exclusions.

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