Skip to main content
Glama
Sign In
mcp-system

mcp-system

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

env_get

Retrieve environment variables from the system. Optionally specify a variable name to get its value, or omit to get all variables.

Instructions

Get environment variables

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
variableNoSpecific variable to get (optional, returns all if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic operation 'Get environment variables' and does not disclose return format, failure modes, or whether it returns all variables when none specified (though the schema covers that). It implies a read-only operation via 'get', but lacks richer context.

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?

The description is a single sentence, 'Get environment variables', which is appropriately sized and front-loaded. There is no extraneous information; every word serves a purpose.

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

Completeness3/5

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

The tool is simple with one optional parameter and no annotations or output schema. While the description and schema cover the basic purpose and parameter, the lack of return format or behavior details leaves gaps. However, for a straightforward getter, this is minimally adequate.

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?

The schema already describes the single 'variable' parameter with 100% coverage, so the baseline is 3. The description adds no additional meaning about how the parameter is used or its optional behavior, relying entirely on 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?

The description states a specific verb 'get' with a clear resource 'environment variables'. It distinguishes itself from siblings like env_set (which sets variables) and system_info (which provides general system information). The scope 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention env_set or any other sibling, nor does it state exclusions or prerequisites. The only implied usage is from the verb 'get', which is not explicit.

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

Deploy Server

Other Tools