Skip to main content
Glama

Load API keys from a .env file

load_env
Idempotent

Loads API keys from a user-named .env file so backends work at once; asks for the path, never for keys, and returns only credential names.

Instructions

Load API keys from a .env file the user names, so their backends work at once. Ask where it is; never ask for a key. Only provider credentials are read, an already-set variable wins, and only names are returned. Set remember (read it on every start) only when the user asks.

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

Input Schema

NameRequiredDescriptionDefault
pathYesThe .env file's path on this machine, as the user gave it, e.g. '~/work/.env'; '~' expands.
rememberNoRead this file on every start too. Only when the user asks for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing filtering ('only provider credentials are read'), precedence ('an already-set variable wins'), and output content ('only names are returned'), which reassures the agent that secret values are not echoed. It also explains the persistent side effect behind readOnlyHint=false, something the annotations alone do not convey.

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?

Four short clauses, front-loaded with the purpose, then interaction rules, then behavioral guarantees. Every sentence carries distinct information with no filler.

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

Completeness5/5

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

For a two-parameter tool with no output schema, the description covers purpose, user interaction, credential scoping, precedence, return content, and persistence opt-in. An agent can invoke it correctly without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the path must come from the user (and must never be a key), and `remember` is a persistence flag tied to an explicit user request. It reinforces rather than merely restates the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — loading API keys from a .env file the user names — plus the outcome ('so their backends work at once'). No sibling in the catalog does this, so no differentiation is required, and the scope of what is loaded is narrowed to provider credentials.

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

Usage Guidelines4/5

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

Gives concrete interaction guidance: 'Ask where it is; never ask for a key,' and gates `remember` on the user explicitly requesting it. There are no sibling alternatives to route against, so the only missing element is an explicit statement of when-not-to-use beyond the remember exclusion.

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