Skip to main content
Glama

scan_project_for_secrets

Read-only

Recursively scan a project for hard-coded secrets and committed env files, returning only file paths, line numbers, and secret types—never secret values.

Instructions

Recursively scan the project (skipping node_modules, .git, build output and binaries) for hard-coded secrets and env files that may be committed. Returns only file paths, line numbers and secret types. Secret values are NEVER returned.

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

Input Schema

NameRequiredDescriptionDefault
pathNoDirectory relative to the project root. Defaults to the root.
max_filesNoMaximum files to scan (default 2000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds genuinely non-obvious behavior: recursion, an explicit skip list (node_modules, .git, build output, binaries), and a hard guarantee that secret values are never returned. That non-return guarantee is exactly the kind of security-relevant trait an agent could not derive from structured fields, though cost/performance expectations beyond max_files are unstated.

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?

Three short sentences, front-loaded with the action and scope, then exclusions, then the return contract. Every sentence carries distinct information with no repetition of the arguments already in the schema.

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?

With no output schema, the description does the necessary work of stating what comes back (file paths, line numbers, secret types) and what never comes back (secret values). The remaining gap is the exact response shape and whether results are aggregated or truncated at max_files, which an agent would have to discover at call time.

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 both parameters (path, max_files) are already documented with defaults and bounds in the schema. The description adds no syntax, path-resolution, or truncation guidance beyond what the schema provides, so the baseline 3 applies.

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 and resource ("Recursively scan the project ... for hard-coded secrets and env files") plus scope details like the skipped directories, so the operation is unmistakable. It stops short of differentiating itself from the sibling check_env_for_secrets, which it never names even though "env files" implies overlap.

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 phrase "that may be committed," which suggests a pre-commit audit context, but there is no explicit when-to-use statement, no exclusions, and no routing to or from check_env_for_secrets. An agent must infer the division of labor between the two scanning tools.

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