Skip to main content
Glama
Systems Manager

Systems Manager

List Env Vars

sm_system_list_env_vars
Read-onlyIdempotent

Lists environment variables on a system so you can inspect runtime configuration and troubleshoot environment-related issues.

Instructions

List env vars (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_list_env_vars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

B3.2/5.0
Behavior3/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 — no mention of whether env vars are system-wide, process-scoped, or how many are returned. It does not contradict the annotations, but it earns little credit for behavior.

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?

The first clause is tight and front-loaded, but the second sentence is pure category boilerplate that consumes roughly half the text without informing the agent. Trimming to just "List environment variables" would lose nothing. Appropriate in length, wasteful in content.

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?

For a zero-parameter, read-only tool with rich annotations and no output schema, the description is barely sufficient. It never clarifies whether the returned variables are the agent-host process environment or system-level variables, which is the one ambiguity an agent could hit. No return-format detail is needed given annotations, so the gap is modest rather than severe.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; baseline 4 applies. The empty schema with additionalProperties=false is self-explanatory. Nothing in the description is needed to call it correctly.

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 definition gives a clear verb+resource pair ("List env vars") that an agent can recognize immediately, and the singular sibling sm_system_get_env_var is implicitly contrasted by list-vs-get. The trailing parenthetical and category sentence ("System operations for managing packages, system health, and updates") are boilerplate that does not sharpen the purpose. Sibling differentiation is left to inference rather than stated.

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 guidance on when to use this tool versus sm_system_get_env_var for a single variable, nor any prerequisite or scope statement. The only usage signal is the word "List", which the agent must interpret on its own. No exclusions or alternatives are named.

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