Skip to main content
Glama
zero-trace-lite

zero-trace-lite

scan_path

Detects leaked secrets and sensitive data in plain-text files or folders, including inline passwords, API keys, database URIs, home paths, and e-mail addresses. Read-only.

Instructions

Report supported leak patterns in a folder or a text file. Reads plain text only: home paths with a login name, common secret-key formats, inline passwords, database URIs with a password, secrets in .claude/settings*.json, e-mail addresses. Read-only.

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": {
      "path": "<path>"
    },
    "name": "scan_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description genuinely adds behavioral information: it declares "Read-only" and discloses the important constraint that only plain text is read, implying binary files are skipped. It does not disclose whether subdirectories are traversed, what happens on a missing/inaccessible path, size limits, or any output/rate behavior.

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?

Two sentences, front-loaded with purpose and followed by a compact enumeration of detected pattern types, ending with the read-only declaration. The pattern list earns its place as it defines detection scope; nothing is redundant.

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 definition covers the essential ground: what it detects, that it takes a directory or file path, that it only reads plain text, and that it is read-only. The main residual gap is output shape (a list of findings?) and whether traversal is recursive.

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 0% and the single parameter is only typed as string, so the description must compensate. It does add useful meaning by stating the path may be either a folder or a text file, but gives no guidance on absolute vs relative paths or accepted file extensions.

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?

Uses a concrete verb ("Report") with a concrete resource ("leak patterns") and scope ("a folder or a text file"), then enumerates the exact pattern classes detected. It does not distinguish itself from the sibling scan_text, so the agent cannot tell from the description alone which of the two to pick for a raw string versus a path.

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?

"Reads plain text only" and the pattern list imply the appropriate use case (secret/credential discovery in files), but there is no explicit when-to-use, no when-not, and no reference to scan_text as the alternative for text input. Guidance is inferable rather than stated.

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

Deploy Server

Other Tools