Skip to main content
Glama

env_compare

Read-only

Compare .env and .env.example files to identify missing, empty, placeholder, extra, and duplicate keys without exposing values.

Instructions

.env vs .env.example: missing, empty, placeholder, extra, duplicate keys. Never prints values.

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

Input Schema

NameRequiredDescriptionDefault
dirNo
envNo
exampleNo
show_keysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

The annotation already declares readOnlyHint=true, so safety is partly covered, but 'Never prints values' adds genuinely useful context beyond it: the agent learns that output is key-name-only and that secrets will not leak into its context. What is missing is behavior on edge cases — absent files, unreadable paths, or whether 'show_keys' changes that value-suppression guarantee.

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?

Two sentences, front-loaded with the comparison target and then the finding categories; the security guarantee lands last as a punchline. Every clause carries information and nothing is padded.

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?

With four undocumented parameters, no output schema, and only a readOnlyHint annotation, the description leaves too much unspecified for the tool's complexity: no defaults for dir/env/example, no description of the returned structure, and no reconciliation of 'show_keys' with the 'never prints values' promise. It is adequate as a one-line elevator pitch but not as a calling contract.

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% across four parameters (dir, env, example, show_keys), and the description explains none of them. A reader can infer that 'env' and 'example' are file paths defaulting to the standard names, but 'dir' (base directory?) and especially 'show_keys' (does it reveal key names despite 'never prints values'?) are left ambiguous in both schema and description.

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 names the concrete resource pair ('.env vs .env.example') and enumerates the exact findings it produces: missing, empty, placeholder, extra, duplicate keys. That is a specific verb-plus-resource statement an agent can act on, though it never differentiates itself from the generic 'diff' sibling that could also compare two files.

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 fixed '.env vs .env.example' framing, which does scope the tool to env-file auditing. There is no explicit statement of when to prefer this over a plain diff, no mention of prerequisites (does the example file need to exist?), and no exclusions.

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