Skip to main content
Glama

thanaton_manage_env

List, set, or delete environment variables for a specific project and target environment, including production, preview, development, or all.

Instructions

List, set, or delete project environment variables.

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": {
      "project_id": "<project_id>",
      "action": "<action>"
    },
    "name": "thanaton_manage_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoEnvironment variable key
valueNoVariable value (for set action)
actionYesAction to perform
project_idYesTarget project ID
environmentNoTarget environment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing about behavior. It does not say whether 'set' overwrites an existing key, whether 'delete' is irreversible, what permissions are needed, how 'environment' scoping affects list versus delete, or what the results look like. For a tool with destructive delete semantics, this is a serious gap.

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?

A single, front-loaded sentence with no padding. However, it is terse to the point of under-specification: the same word count could have carried the most important caveats.

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

Completeness2/5

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

The tool has 5 parameters, 2 enums, conditional field requirements, an unannotated mutation surface, and no output schema; the definition addresses none of these. An agent must open the schema to learn that 'value' only applies to 'set' or what 'environment: all' means for a delete.

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 100% and both enums are documented in the schema, so the schema already explains every parameter. The description adds only the action vocabulary; it does not explain the conditional relationships (value matters only for 'set'; key is unnecessary for 'list'). A baseline of 3 would apply, but the description at least ties the three actions to the parameter set.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific set of verbs (list, set, delete) against a specific resource (project environment variables), so the agent knows what domain the tool covers. It does not differentiate itself from siblings such as thanaton_inject_secrets, which plausibly also manipulates environment variables, so it falls short of a 5.

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 three action names imply when each mode applies, giving implied usage guidance. However, there is no explicit when-to-use/when-not-to-use framing, no mention of prerequisites, and no pointer to a sibling for related operations such as bulk secret injection.

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