Skip to main content
Glama

Check environment variable coverage

bpj_environment_variable_coverage
Read-onlyIdempotent

Compare a public environment template with the variable names present in a deployment. Supply only names for the deployed side.

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": {
      "template": "<template>",
      "present": "<present>"
    },
    "name": "bpj_environment_variable_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
presentYes
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the privacy-relevant instruction to pass names only for the deployed side, which is genuine added context. It does not disclose what the comparison reports (missing vs. extra variables) or how mismatches are surfaced, leaving a behavioral gap.

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 core action and followed by the one constraint that matters. Nothing is redundant or padded.

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 two-parameter, read-only, closed-world check with no output schema, the definition covers what the tool does and how to prepare inputs. The main omission is any hint of what the comparison returns, which matters because there is no output schema to fall back on, but overall it is sufficient to invoke correctly.

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%, so the description carries the burden, and it does clarify the role of each parameter: template is the public .env.example, present is names-only from the deployment. That said, it adds no format or size expectations (one-per-line, length caps) beyond what the schema titles already say, so it only partially compensates.

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 a specific verb and both resources: it compares a public environment template against the variable names present in a deployment. An agent immediately knows this is a coverage/diff check rather than a validator or generator. It does not differentiate itself from the many sibling check tools, but the purpose itself is unambiguous.

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?

"Supply only names for the deployed side" is a real usage constraint that tells the agent to strip values before calling, which is meaningful guidance. However, there is no statement of when to prefer this tool over alternatives or what preconditions apply (e.g. template must be the public example file, not a real .env).

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.