Skip to main content
Glama

gograph_envs

Read-onlyIdempotent

Find all environment variable reads (os.Getenv, os.LookupEnv) in Go code with enclosing function context. Filter by key name substring. Use for documenting required env vars or auditing secrets.

Instructions

Find all environment variable reads in the codebase via os.Getenv, os.LookupEnv, and common config frameworks, with their enclosing function context. Requires .gograph/graph.json — run gograph build . first. Read-only; no side effects. Optional term filters by key name substring (e.g., "DATABASE" matches DATABASE_URL and DATABASE_HOST). WHEN TO USE: When compiling a deployment configuration manifest, documenting required env vars, or auditing what secrets a service reads at startup. NOT TO USE: For reading actual runtime env values (this is static analysis); for database queries (use gograph_sql). RETURNS: List of env key names, calling function, and file/line; empty when no env reads match the filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoOptional filter term (e.g., 'DATABASE' matches DATABASE_URL, DATABASE_HOST, etc.)
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent hints. Description adds prerequisite requirement, no side effects guarantee, and return format details. No contradiction.

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?

Single well-structured paragraph: purpose, prerequisite, safety, parameter, usage guidance, return info. No redundant sentences; every sentence contributes essential information.

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?

Given moderate complexity (1 optional param, no output schema), the description is complete: covers purpose, prerequisite, safety, parameter semantics, usage guidance, and return value. No gaps.

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?

Only one optional parameter with 100% schema coverage. Description adds value by explaining filter behavior (substring matching) and providing example (DATABASE matches DATABASE_URL and DATABASE_HOST), enhancing the schema definition.

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?

Description clearly states it finds environment variable reads via specific functions (os.Getenv, os.LookupEnv, config frameworks) and provides function context. It distinguishes from siblings by noting it is for static analysis contrasts with gograph_sql for database queries.

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

Usage Guidelines5/5

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

Explicitly states when to use (compiling deployment config, documenting env vars, auditing secrets) and when not to use (reading runtime values, database queries). Also includes prerequisite .gograph/graph.json and 'gograph build .'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ozgurcd/gograph'

If you have feedback or need assistance with the MCP directory API, please join our Discord server