Skip to main content
Glama

devops-linux

dotenv_audit_and_example

Audit .env files for duplicate keys, unquoted spaces, weak placeholders, and high-entropy secrets, and generate a safe sanitized .env.example.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 what is detected, but leaves the most consequential behavior ambiguous: whether "generate a safe sanitized .env.example" writes a file to disk or merely returns content, whether the operation is read-only, and how "high-entropy secrets" are flagged (warn vs. block).

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?

A single front-loaded sentence that packs the audit dimensions first and the output artifact second, with no filler. It is dense rather than padded, though the compound clause list makes the two distinct capabilities slightly harder to separate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a dual-mode tool (audit plus example generation) with two undocumented optional parameters, no annotations, and no output schema, the description does too little. It defines the checks well but omits input selection semantics, return shape, and whether any files are written, all of which the agent needs to invoke it correctly.

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 is 0% for both parameters and the description never mentions `text` or `filePath`. It only gestures obliquely at file input via ".env files", leaving the agent to guess that raw text is also accepted, that both are optional, and which one wins if both are supplied.

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 uses a specific verb ("Audit") on a specific resource (".env files") and enumerates the concrete checks: duplicate keys, unquoted spaces, weak placeholders, high-entropy secrets, plus a secondary action to generate a sanitized .env.example. That distinguishes it from the config-format siblings (nginx, k8s, terraform) by file type, though it never explicitly says so.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this tool, no prerequisites, and no mention of alternatives among the many audit/lint siblings. Nothing tells the agent whether to use it pre-commit, in CI, or after editing, nor whether the audit and the .env.example generation can be requested separately.

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