Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_env_set

Idempotent

Set an environment variable for the current server process, affecting only this session and its spawned processes. The change is temporary and lost on restart.

Instructions

Mutating: changes the process environment of the running SassyMCP server. Sets one variable immediately for the server process and anything it spawns from this point on. It does NOT modify system or user environment settings, and the change is lost when the server restarts. Returns the variable name, scope process, and an expiry note. Use it only for values needed during the current session; for permanent configuration change the OS or shell profile instead of calling this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.1
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"sassy_env_setOutput"New value: +"sassy_env_setDictOutput"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it is ephemeral ('lost when the server restarts'), scoped to the process only, returns 'the variable name, scope process, and an expiry note,' and explicitly disclaims system/user modification. These are non-obvious traits the agent could not infer from readOnlyHint=false or idempotentHint=true, and there is no contradiction with annotations.

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 front-loaded with the core mutating behavior, followed by scope, exclusions, return value, and usage guidance. Every sentence adds distinct information with no redundancy or filler, making it efficient and easy to parse.

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

Completeness5/5

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

For a tool with two simple string parameters, an output schema, and annotations that already cover read-only/destructive/idempotent traits, the description supplies everything needed to invoke it correctly: what it does, its ephemeral scope, return value, and an explicit alternative. No critical information is missing.

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 compensate. It frames the two parameters as a variable name and value within the server process scope, giving them meaning beyond the bare titles 'Name' and 'Value.' It stops short of describing edge cases like value formatting or validation, but the core semantics are clear.

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 opens with 'Mutating: changes the process environment of the running SassyMCP server' and states it 'Sets one variable immediately for the server process and anything it spawns from this point on.' This gives a specific verb, resource, and scope, and clearly distinguishes the tool from sassy_env_get/list and permanent-config tools by noting it does NOT touch system or user environment settings.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Use it only for values needed during the current session; for permanent configuration change the OS or shell profile instead of calling this.' This states the when-to-use condition and names the concrete alternative, leaving no ambiguity about 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