Skip to main content
Glama
Sign In
oh-my-mcp

oh-my-mcp

by quyansiyuanwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_env_variable

Retrieve the value of a specified environment variable, with an option to provide a default if the variable is not set.

Instructions

Get an environment variable value.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_env_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the environment variable
defaultNoDefault value if variable not found (default: empty string)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description only states 'Get an environment variable value.' It does not disclose potential side effects, error handling, security implications (e.g., exposing secrets), or any behavioral traits beyond the basic read operation.

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 that is appropriately sized and front-loaded. Every word is necessary, and there is no wasted content.

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?

Given the simplicity of the tool (2 parameters, high schema coverage, and an output schema), the description captures the core purpose. However, it could mention the return type or behavior when the variable is not found, though the default parameter partially addresses that.

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 input schema has 100% description coverage for both parameters ('name' and 'default'). The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Get an environment variable value.' uses a specific verb ('Get') and resource ('environment variable value'), clearly indicating what the tool does. It naturally distinguishes itself from sibling tools like 'list_env_variables' which lists all variables.

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?

No guidance is provided on when to use this tool versus alternatives. While the name implies reading a single variable, there is no explicit context for usage or exclusion of other tools.

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