Skip to main content
Glama

Set environment variable

eurobase_set_env
DestructiveIdempotent

Sets one public (non-secret) environment variable of a permitted project, creating it or replacing its value. targets is required and names where the value is used: build (used only while the app is built), app (used by the running app; App deployments in the dashboard), or both; it replaces the variable's previous targets. A change the running app reads starts a redeploy of the live app release when that release reads its variables at activation (returned as redeploy); otherwise it applies from the next deployment. A change the build reads rebuilds the live release from its source when the grant also has deployments:write (the rebuild is listed by eurobase_list_deployments); otherwise it applies from the next deployment. A variable stored as a secret is refused with ENV_CHANGE_REFUSED: secret values are added and changed by the user in the Eurobase dashboard. Public values can appear in published assets. Setting the same value again changes nothing and starts no second redeploy.

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": {
      "projectId": "<projectId>",
      "key": "<key>",
      "value": "<value>",
      "targets": "<targets>"
    },
    "name": "eurobase_set_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueYes
targetsYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / targets
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "build",
      +      "app"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 2,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "projectId",
      -  "key",
      -  "value"
      -]New value: +[
      +  "projectId",
      +  "key",
      +  "value",
      +  "targets"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, and the description adds real substance beyond them: the ENV_CHANGE_REFUSED guard for secret-stored variables, the deployments:write permission requirement for rebuilds, the returned redeploy signal, and the note that public values can appear in published assets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The write action and targets semantics are front-loaded, and every later sentence carries operational information. Some sentences are long and dense with semicolons, but little is wasted.

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 destructive mutation with no output schema, the description covers side effects, permission gating, refusal cases, idempotency, and the redeploy return signal. An agent has what it needs to call this safely.

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 load. It thoroughly explains targets (build vs app, replacement semantics) and implies key/value purpose, though projectId and the key format constraints remain undocumented beyond 'permitted project'.

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?

States a specific verb and resource: sets one public (non-secret) environment variable of a permitted project, creating or replacing its value. This is clearly distinct from siblings like eurobase_list_env and eurobase_unset_env.

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

Usage Guidelines4/5

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

Explains when the change takes effect (redeploy on activation-read, rebuild with deployments:write, otherwise next deployment) and routes secrets to the dashboard rather than this tool. It does not explicitly contrast with eurobase_unset_env or eurobase_list_env, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.