Skip to main content
Glama
Systems Manager

Systems Manager

Get Env Var

sm_system_get_env_var
Read-onlyIdempotent

Retrieve the value of a specified environment variable to inspect system configuration and support diagnostics or automation.

Instructions

Get env var (sm_system_operations). System operations for managing packages, system health, and updates

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

Input Schema

NameRequiredDescriptionDefault
env_varNoEnvironment variable name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — it doesn't say what is returned, whether unset variables error or return null, or what happens when env_var is omitted. No contradiction with annotations, but no value added either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but half of the text is generic category boilerplate ("System operations for managing packages, system health, and updates") that earns no place in a single-variable getter's description. The remaining text is a bare restatement of the name.

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?

This is a simple one-parameter read tool with strong annotations, but with no output schema the description should explain the return value and the null/omitted-parameter behavior. Neither is present, leaving the agent to guess what a call actually yields.

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 100% and the single optional parameter env_var is documented in the schema, so the baseline of 3 applies. The description adds no interpretation of the parameter, such as whether omitting it returns all variables, which would have been the useful contribution.

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

Purpose2/5

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

"Get env var" essentially restates the tool name and title rather than adding meaning; the only extra content is a parenthetical category tag "(sm_system_operations)". It never distinguishes this from sibling sm_system_list_env_vars, so an agent gets no help telling the single-variable lookup apart from the listing tool.

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?

There is no when-to-use guidance, no indication of when this is preferable to sm_system_list_env_vars, and no prerequisites or exclusions. The trailing sentence about managing packages, system health, and updates is category boilerplate that doesn't direct tool selection.

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