Skip to main content
Glama
Sign In
mcp-system

mcp-system

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

env_set

Set an environment variable for the current process to adjust runtime behavior. Specify the variable name and its value.

Instructions

Set an environment variable for the current process

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": {
      "variable": "<variable>",
      "value": "<value>"
    },
    "name": "env_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesVariable value
variableYesVariable name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the operation ('Set') and scope, but does not mention side effects (e.g., overwriting existing variables), return value, error conditions, or whether the change affects child processes. This is insufficient for a mutating tool with no annotation support.

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, front-loaded sentence that conveys the essential purpose without any filler. Every word contributes to meaning, making it highly concise and appropriately sized for a simple tool.

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 (2 parameters, no output schema), and the description combined with the schema covers the core action and scope. However, because it is a mutating operation with no annotations, missing details about return values and failure modes make it only minimally complete.

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%, with both parameters ('variable' and 'value') described directly in the schema. The description itself does not add extra parameter semantics, so per the rubric it receives the baseline score of 3.

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 uses a specific verb ('Set') and resource ('environment variable') with scope ('for the current process'), clearly distinguishing it from sibling tools like env_get. The purpose is immediately understandable and unambiguous.

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?

The phrase 'for the current process' provides useful context about the scope (non-persistent, process-local), implying when this tool is appropriate. However, it does not explicitly mention alternatives (e.g., env_get) or exclusion cases, so the guidance is primarily implicit.

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