Skip to main content
Glama

set_service_env

Add, update, or remove a hosted service's environment variables; the service restarts with the new values and secrets are stored encrypted and not displayed again.

Instructions

Ortam değişkenlerini (API anahtarları, ayarlar) ekler / değiştirir / siler; servis yeni değerlerle yeniden başlar. Değerler şifreli saklanır ve bir daha GÖSTERİLMEZ. PORT, DATABASE_URL, REDIS_URL, DATA_DIR sistem tarafından verilir. Gizli değerleri koda ya da zip'e koyma — bu aracı kullan.

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": {
      "serviceId": "<serviceId>"
    },
    "name": "set_service_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo
unsetNo
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the key behaviors: the service restarts with the new values (an actual disruption), values are stored encrypted and NEVER shown again (irreversible, unreadable), and some keys are reserved by the system. It does not mention permissions, rate limits, or what a partial-failure response looks like.

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?

Five short clauses, each carrying distinct information: operation set, restart side effect, encryption/non-retrievability, reserved keys, and the push to use this tool for secrets. Front-loaded with the verb and resource; slightly dense with the all-caps emphasis but no filler.

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?

For a mutation tool with no annotations and no output schema, the description covers the essentials an agent needs: what it changes, that it restarts the service, that values become unreadable, and which keys are forbidden. Return shape and error semantics are absent, which is the remaining gap.

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 only 33% (only serviceId is documented in the schema). The description implies the set/unset split through 'adds / changes / deletes', but never explains that `set` is a key→string map and `unset` is an array of key names, nor how they interact in a single call. Partial compensation only.

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 names a specific resource (environment variables such as API keys and settings) and the exact operations (add / change / delete), plus the consequence of the service restarting. It is clearly distinct from list_services, update_service or deploy_service, which do not manage env vars.

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?

It gives explicit guidance on the correct path for secrets ('Gizli değerleri koda ya da zip'e koyma — bu aracı kullan') and warns which keys are system-provided and therefore off-limits (PORT, DATABASE_URL, REDIS_URL, DATA_DIR). It does not name a sibling alternative or exclusion, so it falls short of a 5.

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