Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Environment Variables

get_environment_variables

Retrieve environment variables from the LinuxMCP process and optionally mask secrets by default, so you can inspect runtime configuration without exposing sensitive values.

Instructions

Environment variables of the linuxmcp process.

mask_secrets redacts vars whose name contains KEY/TOKEN/SECRET/ PASSWORD/PWD - set False to see raw values.

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

Input Schema

NameRequiredDescriptionDefault
mask_secretsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description does real work: it discloses a security-relevant default (redaction on), the exact name substrings that trigger masking (KEY/TOKEN/SECRET/PASSWORD/PWD), and how to bypass it. That is precisely the behavioral context an agent needs before deciding whether to expose raw secrets; it only omits whether values reflect process start or live state.

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?

Two sentences with zero filler: the scope comes first, then the redaction semantics and the override. Nothing could be removed without losing information an agent needs.

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

Completeness4/5

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

The tool is simple (one optional boolean, output schema present so return shape needn't be described), and the description covers scope plus the redaction behavior that matters for correct invocation. Only edge details, such as whether the secret-name list is fixed or configurable, are absent.

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 description coverage is 0%, so the description must carry the single parameter, and it does: it explains what mask_secrets does, which variables it affects, and that False reveals raw values. The boolean type and default are left to the schema, which is a minor gap but well within acceptable.

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 description names a specific resource (environment variables) and, importantly, scopes it to the linuxmcp process rather than to a shell session or target system, which separates it from neighbors like get_system_info or get_path_info. The verb is implied by the tool name rather than stated, so it falls just short of a full verb+resource statement.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it should call this to inspect environment variables, and the mask_secrets sentence gives actionable guidance on the safe default versus raw values. There is no explicit when-to-use-this-versus-an-alternative framing or mention of any prerequisite.

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